Triple
T20238007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-21 (Michigan highway) |
E498202
|
entity |
| Predicate | hasRouteNumberSign |
P105053
|
FINISHED |
| Object | M-21 shield |
—
|
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: M-21 shield | Statement: [M-21 (Michigan highway), hasRouteNumberSign, M-21 shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNumberSign Context triple: [M-21 (Michigan highway), hasRouteNumberSign, M-21 shield]
-
A.
routeNumberSignedAs
chosen
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
-
B.
hasRouteNumberingScheme
Indicates that one entity uses or is assigned a particular system or scheme for numbering its routes.
-
C.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
D.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
E.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716b4c148190bf663b8a747fbfa5 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.