Triple

T20527815
Position Surface form Disambiguated ID Type / Status
Subject Todd Union E503986 entity
Predicate city P40 FINISHED
Object Rochester NE NERFINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Rochester | Statement: [Todd Union, city, Rochester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rochester
Context triple: [Todd Union, city, Rochester]
  • A. Rochester
    Rochester is a major city in western New York State known historically for its role in industry, photography, and social reform movements.
  • B. Rochester
    Rochester is a small historic town in southeastern Massachusetts known for its rural character and New England charm.
  • C. Rochester chosen
    Rochester is a major city in southeastern Minnesota known for being the home of the world-renowned Mayo Clinic.
  • D. Rochester
    Rochester is a rural town in northern Victoria, Australia, known for its agricultural community and location near the Campaspe River.
  • E. Rochester
    Rochester is a fictional English surname most famously borne by Mr. Edward Rochester, the brooding Byronic hero in Charlotte Brontë’s novel "Jane Eyre."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e0b4b3a6e08190ae663701f50fab8e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a0677018819085396cc8795a34e9 completed April 20, 2026, 9:53 p.m.
Created at: April 16, 2026, 11:37 a.m.