Triple
T3802636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenexa, Kansas |
E91724
|
entity |
| Predicate | majorHighway |
P385
|
FINISHED |
| Object | Interstate 435 |
E21316
|
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: Interstate 435 | Statement: [Lenexa, Kansas, majorHighway, Interstate 435]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Interstate 435 Context triple: [Lenexa, Kansas, majorHighway, Interstate 435]
-
A.
Interstate 435
chosen
Interstate 435 is a beltway highway that encircles the Kansas City metropolitan area, facilitating regional traffic flow and access to surrounding suburbs.
-
B.
Interstate 135
Interstate 135 is a north–south auxiliary Interstate Highway in Kansas that connects Wichita to Interstate 70 near Salina.
-
C.
Interstate 355
Interstate 355 is a toll highway in the Chicago metropolitan area that serves as a suburban north–south bypass around the city.
-
D.
Interstate 335
Interstate 335 is a segment of the Kansas Turnpike that serves as a key north–south connector route in eastern Kansas.
-
E.
Interstate 25
Interstate 25 is a major north–south U.S. highway running through the Rocky Mountain region, connecting cities from New Mexico through Colorado to Wyoming.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee7bacf2881908198a77063d15d16 |
completed | March 9, 2026, 3:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf88d99da08190996996079b947498 |
completed | March 22, 2026, 6:14 a.m. |
Created at: March 9, 2026, 3:15 p.m.