Triple
T25139020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD5 road |
E629746
|
entity |
| Predicate | hasRoadSignage |
P66816
|
FINISHED |
| Object | departmental road markers |
—
|
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: departmental road markers | Statement: [RD5 road, hasRoadSignage, departmental road markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSignage Context triple: [RD5 road, hasRoadSignage, departmental road markers]
-
A.
hasRoadSign
chosen
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
B.
hasRoadSignConvention
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
C.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
D.
hasHazardSignage
Indicates that appropriate warning or hazard signs are present to alert people to potential dangers associated with the entity.
-
E.
usedOnRoadSigns
Indicates that something (such as a symbol, color, or material) is employed in the design or construction of road signs.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 6:29 a.m.