Triple
T27967617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umweltministerium |
E704766
|
entity |
| Predicate | Zuständigkeitsbereich |
P49097
|
FINISHED |
| Object | nationales Umweltrecht |
—
|
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: nationales Umweltrecht | Statement: [Umweltministerium, Zuständigkeitsbereich, nationales Umweltrecht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Zuständigkeitsbereich Context triple: [Umweltministerium, Zuständigkeitsbereich, nationales Umweltrecht]
-
A.
areaOfAuthority
chosen
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
B.
territorialResponsibility
Indicates that an entity holds authority or obligation over managing, protecting, or governing a specific geographic area or territory.
-
C.
scopeOfDuty
Indicates the range or extent of responsibilities, tasks, or obligations that an entity is expected or authorized to perform.
-
D.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
E.
affectedJurisdictionOver
Indicates that one entity’s authority, control, or legal power extends over and impacts the jurisdiction 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 7:36 p.m.