Triple
T15055591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 67 |
E379481
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Festus, Missouri |
E840223
|
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: Festus, Missouri | Statement: [U.S. Route 67, passesThrough, Festus, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Festus, Missouri Context triple: [U.S. Route 67, passesThrough, Festus, Missouri]
-
A.
Festus, Missouri
chosen
Festus, Missouri is a small city in Jefferson County that forms part of the greater St. Louis metropolitan area.
-
B.
Neosho, Missouri
Neosho, Missouri is a small city in southwestern Missouri known for its historic downtown, natural springs, and role as the county seat of Newton County.
-
C.
Sibley, Missouri
Sibley, Missouri is a small village in western Missouri known for its proximity to the historic Fort Osage site along the Missouri River.
-
D.
Calhoun, Missouri
Calhoun, Missouri is a small rural village located in Henry County in the west-central region of the state.
-
E.
Freeman, Missouri
Freeman, Missouri is a small rural city located in Cass County in western Missouri, United States.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda937f788190899d81bbb2084443 |
completed | April 15, 2026, 12:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff755bbe608190a9a565218eee7005 |
completed | May 9, 2026, 5:56 p.m. |
Created at: April 10, 2026, 3:01 a.m.