Triple
T3809529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 41 |
E93095
|
entity |
| Predicate | formerDesignationInSection |
P12531
|
FINISHED |
| Object | U.S. Route 41W |
—
|
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: U.S. Route 41W | Statement: [U.S. Route 41, formerDesignationInSection, U.S. Route 41W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDesignationInSection Context triple: [U.S. Route 41, formerDesignationInSection, U.S. Route 41W]
-
A.
formerDesignation
chosen
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
subsequentDesignation
Indicates that one designation or status follows and replaces another in a sequence or timeline.
-
D.
exportDesignation
Indicates that something is assigned a specific status or classification for export-related purposes, such as regulatory, legal, or logistical handling.
-
E.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.