Triple
T12142516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 440 (Arkansas) |
E289222
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
I-440
I-440 is an auxiliary Interstate Highway that forms part of the beltway around Little Rock, Arkansas, helping route traffic around the city rather than through its downtown core.
|
E964315
|
NE FINISHED |
How this triple was built (4 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-440 | Statement: [Interstate 440 (Arkansas), abbreviation, I-440]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-440 Context triple: [Interstate 440 (Arkansas), abbreviation, I-440]
-
A.
I-4
I-4 is a major east–west Interstate Highway in Florida that connects Tampa, Orlando, and Daytona Beach.
-
B.
I-390
I-390 is a toll highway in northeastern Illinois that serves as a major east–west connector in the Chicago metropolitan area.
-
C.
I-391
I-391 is a short auxiliary Interstate Highway in western Massachusetts that connects Interstate 91 in Chicopee to Holyoke, serving as a spur route into the city.
-
D.
I-640
I-640 is an auxiliary Interstate Highway that serves as a bypass route around Knoxville, Tennessee.
-
E.
I-215
I-215 is a beltway auxiliary Interstate Highway that loops around the Salt Lake City metropolitan area in Utah, connecting several major freeways and suburbs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: I-440 Triple: [Interstate 440 (Arkansas), abbreviation, I-440]
Generated description
I-440 is an auxiliary Interstate Highway that forms part of the beltway around Little Rock, Arkansas, helping route traffic around the city rather than through its downtown core.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: I-440 Target entity description: I-440 is an auxiliary Interstate Highway that forms part of the beltway around Little Rock, Arkansas, helping route traffic around the city rather than through its downtown core.
-
A.
I-4
I-4 is a major east–west Interstate Highway in Florida that connects Tampa, Orlando, and Daytona Beach.
-
B.
I-390
I-390 is a toll highway in northeastern Illinois that serves as a major east–west connector in the Chicago metropolitan area.
-
C.
I-391
I-391 is a short auxiliary Interstate Highway in western Massachusetts that connects Interstate 91 in Chicopee to Holyoke, serving as a spur route into the city.
-
D.
I-640
I-640 is an auxiliary Interstate Highway that serves as a bypass route around Knoxville, Tennessee.
-
E.
I-215
I-215 is a beltway auxiliary Interstate Highway that loops around the Salt Lake City metropolitan area in Utah, connecting several major freeways and suburbs.
- F. None of above. chosen
Provenance (5 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915a9838081909622cc14df2a2582 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f69501348190a9ac090c7db37c20 |
completed | May 2, 2026, 1:05 p.m. |
| NEDg | Description generation | batch_69f5ff815b748190932bfe163ea2847d |
completed | May 2, 2026, 1:43 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f60185ce8c8190abe3b1f633aac55d |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 8, 2026, 9:49 p.m.