Triple
T37334972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 75 |
E926865
|
entity |
| Predicate | formerDesignationRelatedTo |
P12531
|
FINISHED |
| Object | U.S. Route 75 |
—
|
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 75 | Statement: [Texas State Highway 75, formerDesignationRelatedTo, U.S. Route 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDesignationRelatedTo Context triple: [Texas State Highway 75, formerDesignationRelatedTo, U.S. Route 75]
-
A.
formerDesignation
chosen
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
C.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
-
D.
modernDesignation
Indicates the current or contemporary name, label, or classification now used for something that previously had a different designation.
-
E.
previousDesignationIncludes
Indicates that an entity’s earlier or former official name, title, or designation contained the specified value.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:16 p.m.