Triple

T8517684
Position Surface form Disambiguated ID Type / Status
Subject Snodland E201615 entity
Predicate locatedBetween P1262 FINISHED
Object Rochester E116344 NE FINISHED

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: [Snodland, locatedBetween, Rochester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rochester
Context triple: [Snodland, locatedBetween, Rochester]
  • A. Rochester
    Rochester is a rural town in northern Victoria, Australia, known for its agricultural community and location near the Campaspe River.
  • B. Rochester chosen
    Rochester is a historic cathedral city and former market town in Kent, England, known for its Norman castle, Romanesque cathedral, and strong associations with the novelist Charles Dickens.
  • C. Rochester
    Rochester is a small borough in western Pennsylvania situated along the Ohio River in Beaver County.
  • D. Rochester
    Rochester is a small village located in Lorain County in the U.S. state of Ohio.
  • E. Rochester
    Rochester is a major city in western New York State known historically for its role in industry, photography, and social reform movements.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca8321bb44819081b74df0b710276d completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe626787c819087e72dd76b2d9310 completed March 31, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea82225148190b9dd190655114c8a completed April 2, 2026, 5:32 p.m.
Created at: March 30, 2026, 6:15 p.m.