Triple
T20902852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 83 |
E514713
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | I-83 |
—
|
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-83 | Statement: [Interstate 83, hasAbbreviation, I-83]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-83 Context triple: [Interstate 83, hasAbbreviation, I-83]
-
A.
I-83
chosen
I-83 is a major north–south Interstate Highway in the eastern United States that connects Baltimore, Maryland, with Harrisburg, Pennsylvania.
-
B.
I-84
I-84 is a major east–west Interstate Highway in the northwestern United States, running through Oregon and Idaho as a key regional transportation corridor.
-
C.
I-278
I-278 is a major auxiliary Interstate Highway in New York City that connects several boroughs via routes such as the Bruckner, Brooklyn-Queens, and Staten Island expressways.
-
D.
Interstate 184
Interstate 184 is a short auxiliary Interstate Highway in Boise, Idaho, serving as a spur that connects downtown Boise with Interstate 84.
-
E.
Interstate 86
Interstate 86 is an east–west U.S. Interstate Highway in New York and Pennsylvania that serves as a major corridor through the Southern Tier region.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fd7e4481909088b7f74ba24549 |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.