Triple
T28123133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havlíčkův Brod District |
E710846
|
entity |
| Predicate | roadSignStyle |
P164058
|
FINISHED |
| Object | Czech 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: Czech road signs | Statement: [Havlíčkův Brod District, roadSignStyle, Czech road signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSignStyle Context triple: [Havlíčkův Brod District, roadSignStyle, Czech road signs]
-
A.
roadSignPrefix
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
-
B.
roadSignColor
Indicates the color attribute associated with a particular road sign.
-
C.
roadSignCode
Indicates the specific regulatory or informational code assigned to a road sign that defines its meaning or instruction.
-
D.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
E.
hasRoadSignShape
Indicates that one entity possesses or exhibits the geometric shape characteristic of a particular road sign.
- F. None of above. chosen
Provenance (4 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 9:18 p.m.