Triple
T33695596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A80 |
E863298
|
entity |
| Predicate | supersededFunction |
P5925
|
FINISHED |
| Object | long‑distance through traffic now carried by M80 |
—
|
LITERAL 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: long‑distance through traffic now carried by M80 | Statement: [A80, supersededFunction, long‑distance through traffic now carried by M80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededFunction Context triple: [A80, supersededFunction, long‑distance through traffic now carried by M80]
-
A.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
formerFunction
chosen
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
isDeprecatedInFavorOf
Indicates that something is considered obsolete or no longer recommended because it has been superseded by a specified alternative.
-
D.
supersededSpecificationIn
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
E.
supersededByDate
Indicates the date on which something is replaced or rendered obsolete by a newer version or successor.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1:43 a.m.