Triple
T27957498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkehrsministerium |
E703590
|
entity |
| Predicate | überwacht |
P20679
|
FINISHED |
| Object | Einhaltung von Verkehrsgesetzen |
—
|
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: Einhaltung von Verkehrsgesetzen | Statement: [Verkehrsministerium, überwacht, Einhaltung von Verkehrsgesetzen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: überwacht Context triple: [Verkehrsministerium, überwacht, Einhaltung von Verkehrsgesetzen]
-
A.
oversee
chosen
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
B.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
C.
يراقب
Indicates that one entity is watching, monitoring, or observing another entity or situation.
-
D.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
E.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
- 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_69f63b00473c8190b718fe3d0a717e32 |
completed | May 2, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:29 p.m.