Triple
T22864289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route 251 |
E567007
|
entity |
| Predicate | hasRouteSignShape |
P20601
|
FINISHED |
| Object | 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: shield | Statement: [National Route 251, hasRouteSignShape, shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteSignShape Context triple: [National Route 251, hasRouteSignShape, shield]
-
A.
hasRoadSignShape
Indicates that one entity possesses or exhibits the geometric shape characteristic of a particular road sign.
-
B.
routeSymbolShape
chosen
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
-
C.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
D.
hasRouteAlignment
Indicates that there is a defined spatial or geometric alignment associated with a route or pathway.
-
E.
hasRoadSignConvention
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17effd93081909f2c9a8857a8728b |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.