Triple
T24725400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M23 SBS |
E618131
|
entity |
| Predicate | agencyRouteDesignation |
P26087
|
FINISHED |
| Object | M23 SBS |
—
|
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 SBS | Statement: [M23 SBS, agencyRouteDesignation, M23 SBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agencyRouteDesignation Context triple: [M23 SBS, agencyRouteDesignation, M23 SBS]
-
A.
auxiliaryRouteDesignation
Indicates that a route is designated as an auxiliary (e.g., spur, loop, bypass) of a primary route.
-
B.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
C.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
-
D.
routeNumberingAuthority
chosen
Indicates the authority or organization responsible for assigning and managing the official number designation of a route.
-
E.
roadAssociatedWith
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:56 a.m.