Triple
T2131897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führer and Reich Chancellor |
E46559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | head of government title |
C3899
|
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: head of government title Context triple: [Führer and Reich Chancellor, instanceOf, head of government title]
-
A.
head of government position
chosen
A head of government position is a formal political role that holds primary executive authority to lead and manage the administration and implement public policy within a sovereign state or jurisdiction.
-
B.
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.
-
C.
head of state office
The head of state office is an organizational unit responsible for supporting, advising, and coordinating the official duties, ceremonial functions, and administrative activities of a nation's head of state.
-
D.
head of state position
A head of state position is a formal role within a political system occupied by an individual who serves as the chief public representative and symbolic or executive leader of a sovereign state.
-
E.
head of state role
A head of state role represents the highest-ranking official who symbolically embodies the continuity and legitimacy of a sovereign state and may perform ceremonial, diplomatic, and/or executive functions.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:44 p.m.