Triple
T22866778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regierungspräsident |
E567076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional administrative head |
C25599
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regional administrative head Context triple: [Regierungspräsident, instanceOf, regional administrative head]
-
A.
executive head of province
chosen
The executive head of province is the highest-ranking official responsible for leading the provincial government, implementing laws and policies, and overseeing administration within the province.
-
B.
territorial leader
A territorial leader is an individual or entity that holds authority over a defined geographic area, managing its resources, people, and governance within recognized boundaries.
-
C.
regional directors
Regional directors are senior managers responsible for overseeing operations, strategy implementation, and performance across multiple locations within a defined geographic area.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
head of government office
The head of government office is an organizational unit that supports and coordinates the activities, decision-making, and administration of a jurisdiction’s chief executive (such as a prime minister or president) by providing policy advice, strategic planning, and operational management.
- F. None of above.
Provenance (1 batch)
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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:38 p.m.