Triple
T1964678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blomberg |
E42660
|
entity |
| Predicate | roadSignStandard |
P1739
|
FINISHED |
| Object | German 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: German road signage | Statement: [Blomberg, roadSignStandard, German road signage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSignStandard Context triple: [Blomberg, roadSignStandard, German road signage]
-
A.
roadSignCode
Indicates the specific regulatory or informational code assigned to a road sign that defines its meaning or instruction.
-
B.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
-
C.
signageStandard
chosen
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
D.
hasTrafficSignals
Indicates that traffic control signals are present at or associated with a given location or roadway feature.
-
E.
roadTrafficRuleJurisdiction
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3ada4148190ad830d4a3d7fd662 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.