Triple
T17329061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-275 |
E420764
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | I-275 |
—
|
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-275 | Statement: [I-275, abbreviation, I-275]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-275 Context triple: [I-275, abbreviation, I-275]
-
A.
I-275
I-275 is an auxiliary Interstate Highway that forms part of the beltway system around the Detroit metropolitan area in southeastern Michigan.
-
B.
Interstate 275
chosen
Interstate 275 is a bypass freeway in southeastern Michigan that forms part of the outer beltway around the Detroit metropolitan area.
-
C.
Interstate 275
Interstate 275 is a short auxiliary Interstate Highway in Knoxville, Tennessee, serving as a connector route through the city between major regional interstates.
-
D.
Interstate 275
Interstate 275 is a major auxiliary Interstate Highway that serves as a bypass and urban loop around the Tampa Bay area in Florida.
-
E.
I-235
I-235 is an auxiliary Interstate Highway that serves as a bypass route around Wichita, Kansas.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d50b308190a255874a9b8f3cd3 |
completed | April 19, 2026, 2:11 a.m. |
Created at: April 10, 2026, 5:43 a.m.