Triple

T20489033
Position Surface form Disambiguated ID Type / Status
Subject Lincolnville, Maine E502687 entity
Predicate traversedBy P225 FINISHED
Object Maine State Route 173 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: Maine State Route 173 | Statement: [Lincolnville, Maine, traversedBy, Maine State Route 173]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maine State Route 173
Context triple: [Lincolnville, Maine, traversedBy, Maine State Route 173]
  • A. Maine State Route 173 chosen
    Maine State Route 173 is a state highway in Maine that connects several communities in the coastal region of the state.
  • B. Maine State Route 171
    Maine State Route 171 is a state highway in Maine that serves as a local connector route within the state’s numbered highway network.
  • C. Maine State Route 177
    Maine State Route 177 is a state highway in Maine that serves as a regional connector road within the state's numbered route network.
  • D. Maine State Route 172
    Maine State Route 172 is a state highway in Maine that connects the towns of Ellsworth and Blue Hill in Hancock County.
  • E. Maine State Route 170
    Maine State Route 170 is a state highway in Maine that serves as a regional connector for local communities within the state’s road network.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69b5d93ec81908259696359090b35 completed April 20, 2026, 9:32 p.m.
Created at: April 16, 2026, 11:34 a.m.