Mark two location mentions using the exact character-offset contract. How would you check your result?

Instruction: Use the supplied source and offset contract. Return both LOCATION spans, then explain how you would check their boundaries without changing the text.

Context:

Practice precise entity labeling using an explicit offset convention. Explain how you would catch a boundary error before submitting the spans.

Fictional practice task

Exact source text:

Ship from York to New York.

Annotate both complete location mentions as LOCATION. Offsets count Unicode code points from zero in this exact string. Use half-open intervals [start, end), so the start is included and the end is excluded. Spaces and punctuation count as characters. Do not trim, normalize or otherwise change the source. Return each mention with its start and end, then explain how you would verify the spans. This is an exercise-specific offset contract.

Updated

Example Answer

I’d label York as LOCATION with start 10 and end 14, and New York as LOCATION with start 18 and end 26. The end is exclusive, so neither span includes the following space or final period. I’d treat New York as one complete mention rather than adding a third annotation for the York inside it.

I’d check both spans against the unchanged source: slicing from 10 to 14 must return York, and slicing from 18 to 26 must return New York. I’d also check the annotation preview to make sure the highlights cover exactly those words. This task counts Unicode code points, so I wouldn’t substitute a byte count or a different tool’s offset convention. If the export and preview disagreed, I’d resolve that before submitting.

Checked result

  • York: LOCATION, start 10, exclusive end 14. Check: source[10:14] returns York.
  • New York: LOCATION, start 18, exclusive end 26. Check: source[18:26] returns New York.

Make it your own

If you have used an annotation tool, name the check you actually performed: inspecting highlighted spans, comparing an export with the source, or validating the tool’s offset units. If this is your first exercise, explain these checks as a proposed method rather than claiming prior project experience.

Why this works

The answer supplies the actual labels and boundaries, then checks them against the source. It distinguishes the full New York mention from its embedded word and follows this exercise’s indexing contract rather than an assumed default.

Interviewer follow-up

What would you do if a highlighted span looked correct but the exported offsets were different?

I’d compare the original source, the tool’s stored text and the export’s documented offset convention. The display could look right while using different indexing units or an altered copy of the text. I’d reproduce the mismatch with an approved example and report the tool or contract issue through the project channel. I wouldn’t manually shift every offset until I understood what caused the difference.

Assessment criteria

  • Strong: Returns both correct LOCATION spans; verifies exact source slices and exclusive ends; avoids an extra nested mention; explains how to check the tool’s units without changing the source.
  • Adequate: Returns the two correct spans and explains at least one reliable boundary check, with no source edits or invented third location.
  • Weak: Counts words instead of characters, includes adjacent punctuation, labels only the inner York in New York, or changes the text before counting.

A tempting weak answer

“I’d highlight the two names and let the tool work out the offsets.”

A tool may help, but this answer never verifies the exported contract. A correct-looking highlight does not establish that the stored offsets use the required units or boundaries.

References

The practice text and offset convention are fictional. The public role description illustrates text annotation work; it does not prescribe this exercise’s convention.

Your preparation path

Choose the track that matches the role. Work through its questions in order, then explain each answer in your own words.

Try the 20 minute mock assessment. Use the fictional cases to practice; the self-check is not an employer's hiring benchmark.

Related Questions