Triple
T35109348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberpräsident of Hesse-Nassau |
E1013242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial administrative position |
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: provincial administrative position Context triple: [Oberpräsident of Hesse-Nassau, instanceOf, provincial administrative position]
-
A.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
B.
provincial authority
A provincial authority is a regional governing body responsible for administering laws, policies, and public services within a specific province under a broader national framework.
-
C.
colonial-style administrative position
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central power.
-
D.
municipal government position
A municipal government position is a role within a city or local government responsible for administering public services, implementing local policies, and managing community resources and regulations.
-
E.
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.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.