Triple
T19945131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunma Prefectural Route 28 |
E479402
|
entity |
| Predicate | hasRoadSignStandard |
P103519
|
FINISHED |
| Object | Japanese road signage standards |
—
|
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 signage standards | Statement: [Gunma Prefectural Route 28, hasRoadSignStandard, Japanese road signage standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSignStandard Context triple: [Gunma Prefectural Route 28, hasRoadSignStandard, Japanese road signage standards]
-
A.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
B.
hasRoadSignShape
Indicates that one entity possesses or exhibits the geometric shape characteristic of 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.
routeMarkingStandard
chosen
Indicates the standard or convention used to mark or signpost a particular route.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6654f481908089e1d66e17e024 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.