Triple
T27967529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bauministerium |
E704765
|
entity |
| Predicate | hatZuständigkeit |
P636
|
FINISHED |
| Object | Bauwesen |
—
|
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: Bauwesen | Statement: [Bauministerium, hatZuständigkeit, Bauwesen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatZuständigkeit Context triple: [Bauministerium, hatZuständigkeit, Bauwesen]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
territorialResponsibility
Indicates that an entity holds authority or obligation over managing, protecting, or governing a specific geographic area or territory.
-
C.
accountabilityTo
Indicates that one entity is responsible for explaining, justifying, or answering for its actions, decisions, or outcomes to another entity.
-
D.
زمن_المسؤولية
Indicates the time period during which an entity holds responsibility for an action, event, or obligation.
-
E.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b323ea48190917e104d4d5fb1bf |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:36 p.m.