Triple
T11805729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 54 |
E280741
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Nevada, Missouri |
E152612
|
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: Nevada, Missouri | Statement: [U.S. Route 54, connectsCity, Nevada, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nevada, Missouri Context triple: [U.S. Route 54, connectsCity, Nevada, Missouri]
-
A.
Nevada, Missouri
chosen
Nevada, Missouri is a small city in western Missouri that serves as the county seat and regional hub for Vernon County.
-
B.
California, Missouri
California, Missouri is a small city in Moniteau County known for its rural Midwestern character and role as a local hub in central Missouri.
-
C.
Nevada, Iowa
Nevada, Iowa is a small city in Story County that serves as a residential and commercial hub in central Iowa, near the larger city of Ames.
-
D.
Nevada, Texas
Nevada, Texas is a small rural city in Collin County known for its quiet residential character within the Dallas–Fort Worth metropolitan area.
-
E.
Lebanon, Missouri
Lebanon, Missouri is a small city in Laclede County known as a regional hub along historic Route 66 in central Missouri.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5c8324481909a54852a9bb714e0 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1315b4b1481908106984a1362be89 |
completed | April 28, 2026, 10:14 p.m. |
Created at: April 8, 2026, 9:42 p.m.