Triple
T13983781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-540 |
E336380
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | I-540 |
E336380
|
NE FINISHED |
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-540 | Statement: [I-540, abbreviation, I-540]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-540 Context triple: [I-540, abbreviation, I-540]
-
A.
I-540
chosen
I-540 is a designation used for auxiliary Interstate highways in the United States, most notably around the Raleigh, North Carolina area.
-
B.
I-530
I-530 is a short Interstate Highway in Arkansas that connects Little Rock to Pine Bluff, serving as an important regional transportation corridor.
-
C.
I-990
I-990 is a short auxiliary Interstate Highway in the Buffalo, New York metropolitan area, serving as a spur route connecting the region to Interstate 290.
-
D.
I-220
I-220 is an auxiliary Interstate Highway in the United States that serves as a bypass or loop around a primary Interstate route.
-
E.
I-110
I-110 is a short auxiliary Interstate Highway in Florida that connects downtown Pensacola to Interstate 10.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea2e8808190a1203a6386224bd8 |
completed | April 14, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac942ba481908858d7f214085b5f |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:18 p.m.