Triple
T20103699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-190 (Massachusetts) |
E496612
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | I-190 |
—
|
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-190 | Statement: [I-190 (Massachusetts), abbreviation, I-190]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-190 Context triple: [I-190 (Massachusetts), abbreviation, I-190]
-
A.
I-190
chosen
I-190 is a short auxiliary Interstate Highway in Massachusetts that connects Worcester to the Leominster–Fitchburg area and links to I-290 and Route 2.
-
B.
I-190
I-190 is a short auxiliary Interstate Highway in Illinois that connects Interstate 90 to Chicago O'Hare International Airport.
-
C.
I-229
I-229 is an auxiliary Interstate Highway that serves as a bypass route around Sioux Falls in southeastern South Dakota.
-
D.
I-229
I-229 is a short auxiliary Interstate Highway in Missouri that serves as a bypass and business route around downtown St. Joseph.
-
E.
I-520
I-520 is an auxiliary Interstate Highway that forms a partial beltway around Augusta, Georgia and North Augusta, South Carolina.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6667170a4819085d07a4188ded541 |
completed | April 20, 2026, 5:46 p.m. |
Created at: April 11, 2026, 11:27 p.m.