Triple
T948333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Rock, Arkansas |
E20462
|
entity |
| Predicate | isServedBy |
P1293
|
FINISHED |
| Object | Interstate 630 |
E396838
|
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: Interstate 630 | Statement: [Little Rock, Arkansas, isServedBy, Interstate 630]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Interstate 630 Context triple: [Little Rock, Arkansas, isServedBy, Interstate 630]
-
A.
Interstate 630
chosen
Interstate 630 is an east–west auxiliary Interstate Highway serving as a major commuter route through Little Rock, Arkansas.
-
B.
Interstate 635
Interstate 635 is a major beltway and commuter freeway serving the Dallas–Fort Worth metropolitan area in Texas.
-
C.
Interstate 635
Interstate 635 is a short auxiliary Interstate Highway in the Kansas City metropolitan area that serves as a bypass and connector route between Kansas and Missouri.
-
D.
Interstate 610
Interstate 610 is a beltway freeway encircling central Houston, Texas, serving as a major loop that connects multiple radial highways and facilitates regional traffic flow.
-
E.
Interstate 496
Interstate 496 is an auxiliary Interstate Highway that serves as a key urban connector and bypass route through Lansing, Michigan.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bf9bb88190a79b2db698613a8d |
completed | March 1, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bd677fd8a481909455b2a02830bcc6 |
completed | March 20, 2026, 3:28 p.m. |
Created at: March 1, 2026, 7:40 p.m.