Triple
T19745554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 385 |
E474239
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | I-385 |
—
|
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-385 | Statement: [Interstate 385, abbreviation, I-385]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-385 Context triple: [Interstate 385, abbreviation, I-385]
-
A.
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.
-
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.
Interstate 385
chosen
Interstate 385 is a major freeway in South Carolina that connects the city of Greenville with Interstate 26, serving as a key route between the Upstate region and Columbia/Charleston corridors.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529387ac819094e4d66d630e8b98 |
completed | April 20, 2026, 4:21 p.m. |
Created at: April 10, 2026, 1:47 p.m.