Triple
T24142848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route 211 |
E598290
|
entity |
| Predicate | usesRoadSignSystem |
P142975
|
FINISHED |
| Object | Japanese road signs |
—
|
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: Japanese road signs | Statement: [National Route 211, usesRoadSignSystem, Japanese road signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoadSignSystem Context triple: [National Route 211, usesRoadSignSystem, Japanese road signs]
-
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.
usedOnRoadSigns
Indicates that something (such as a symbol, color, or material) is employed in the design or construction of road signs.
-
D.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
E.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00832148190b40b904d514a286b |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.