Triple
T33696203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M23 SBS |
E863318
|
entity |
| Predicate | previousRouteDesignation |
P22310
|
FINISHED |
| Object | M23 |
—
|
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: M23 | Statement: [M23 SBS, previousRouteDesignation, M23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRouteDesignation Context triple: [M23 SBS, previousRouteDesignation, M23]
-
A.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
B.
routeDesignationOf
Indicates that one entity is the official route number, code, or designation assigned to another entity representing a transportation route.
-
C.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
D.
formerRouteNumber
chosen
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
E.
previousStreetName
Indicates that one street name was formerly used for a street that now has a different, current name.
- 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_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:43 a.m.