Triple
T24147538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 476 |
E598426
|
entity |
| Predicate | freewaySectionNickname |
P66454
|
FINISHED |
| Object | Blue Route |
—
|
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: Blue Route | Statement: [Interstate 476, freewaySectionNickname, Blue Route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freewaySectionNickname Context triple: [Interstate 476, freewaySectionNickname, Blue Route]
-
A.
highwaySectionName
chosen
Indicates the specific name assigned to a particular section or segment of a highway.
-
B.
hasStreetNickname
Indicates that an entity is known by a particular informal or colloquial name used on the street or in everyday speech.
-
C.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
-
D.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
E.
ropewayName
Indicates the name assigned to a ropeway (such as a cable car or aerial lift) associated with the subject.
- F. None of above.
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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00c42288190843962f9476a94a1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.