Triple
T2357503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landtag of Württemberg |
E47589
|
entity |
| Predicate | oversightMethod |
P15245
|
FINISHED |
| Object | interpellations to ministers |
—
|
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: interpellations to ministers | Statement: [Landtag of Württemberg, oversightMethod, interpellations to ministers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversightMethod Context triple: [Landtag of Württemberg, oversightMethod, interpellations to ministers]
-
A.
oversightFocus
Indicates that one entity’s oversight, supervision, or monitoring activities are specifically directed toward another entity or aspect.
-
B.
oversightScope
Indicates the range or extent of responsibilities and activities that fall under an entity’s oversight or supervisory authority.
-
C.
oversightTools
chosen
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
D.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
E.
scrutinyMethods
Indicates the methods or procedures used to examine, inspect, or critically evaluate something.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc71f767481908dfa9be209ea3c5a |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.