Triple
T31506517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B2162 road |
E803829
|
entity |
| Predicate | hasRoadSignageStandard |
P142975
|
FINISHED |
| Object | United Kingdom road signage |
—
|
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: United Kingdom road signage | Statement: [B2162 road, hasRoadSignageStandard, United Kingdom road signage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSignageStandard Context triple: [B2162 road, hasRoadSignageStandard, United Kingdom road signage]
-
A.
hasRoadSignConvention
chosen
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
B.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
C.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
D.
usedOnRoadSigns
Indicates that something (such as a symbol, color, or material) is employed in the design or construction of road signs.
-
E.
hasRoadSignShape
Indicates that one entity possesses or exhibits the geometric shape characteristic of 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 30, 2026, 9:47 p.m.