Triple
T22206917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gratiot Avenue |
E548834
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | I-375 |
—
|
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: I-375 | Statement: [Gratiot Avenue, hasJunctionWith, I-375]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-375 Context triple: [Gratiot Avenue, hasJunctionWith, I-375]
-
A.
I-375
chosen
I-375 is a short auxiliary Interstate Highway in downtown Detroit, Michigan, connecting I-75 to the city's central business district and riverfront.
-
B.
I-376
I-376 is an Interstate Highway in western Pennsylvania that connects Pittsburgh to its international airport and the Pennsylvania Turnpike.
-
C.
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.
-
D.
I-235
I-235 is an auxiliary Interstate Highway that serves as a bypass route around Wichita, Kansas.
-
E.
I-635
I-635 is an auxiliary Interstate Highway that serves as a major beltway and bypass route around parts of the Dallas–Fort Worth metropolitan area in Texas.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2936a481909aa84c7983ed49ee |
completed | April 28, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:36 p.m.