Triple
T5170596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-435 |
E116666
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | I-635 |
E360205
|
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: I-635 | Statement: [I-435, connectsTo, I-635]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-635 Context triple: [I-435, connectsTo, I-635]
-
A.
I-696
I-696 is an east–west interstate highway in the Detroit metropolitan area of Michigan, serving as a key commuter and bypass route through suburbs including Southfield.
-
B.
I-335
I-335 is a segment of the Kansas Turnpike that forms part of the Interstate Highway System, connecting Emporia and Topeka in eastern Kansas.
-
C.
I-375
I-375 is a short auxiliary Interstate Highway in downtown Detroit, Michigan, connecting I-75 to the city's central business district and riverfront.
-
D.
I-235
I-235 is an auxiliary Interstate Highway that serves as a bypass route around Wichita, Kansas.
-
E.
Interstate 635
chosen
Interstate 635 is a short auxiliary Interstate Highway in the Kansas City metropolitan area that serves as a bypass and connector route between Kansas and 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794f44248190a3a90c92208104a7 |
completed | March 20, 2026, 4:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee077effc8190bdd5771db64d1578 |
completed | March 21, 2026, 6:16 p.m. |
Created at: March 20, 2026, 1:45 p.m.