Triple
T27957474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsministerium |
E703590
|
entity |
| Predicate | hatAufgabe |
P129422
|
FINISHED |
| Object | Regulierung des Verkehrs |
—
|
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: Regulierung des Verkehrs | Statement: [Verkehrsministerium, hatAufgabe, Regulierung des Verkehrs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatAufgabe Context triple: [Verkehrsministerium, hatAufgabe, Regulierung des Verkehrs]
-
A.
hatTeil
Indicates that something is a part or component of something else.
-
B.
homeWork
Indicates that one entity assigns, has, or is responsible for homework in relation to another entity.
-
C.
targetTask
chosen
Indicates that one entity is the specific task or objective that another entity is aiming to perform, achieve, or operate on.
-
D.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
E.
hatOrt
Indicates that something is located at or associated with a specific place or location.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:29 p.m.