Triple
T25509693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eickeloh |
E639339
|
entity |
| Predicate | roadTrafficLaw |
P7767
|
FINISHED |
| Object | German road traffic regulations (StVO) |
—
|
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 traffic regulations (StVO) | Statement: [Eickeloh, roadTrafficLaw, German road traffic regulations (StVO)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTrafficLaw Context triple: [Eickeloh, roadTrafficLaw, German road traffic regulations (StVO)]
-
A.
roadTrafficRuleJurisdiction
chosen
Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
-
B.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
C.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
D.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
E.
servesGovernmentTraffic
Indicates that an entity provides services or functionality specifically for government-related network or data traffic.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f809726081908ae4122cd4e581c1 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:48 p.m.