Triple
T16925326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime_Minister_of_Belize |
E410558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | head_of_government_role |
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_role Context triple: [Prime_Minister_of_Belize, instanceOf, head_of_government_role]
-
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 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.
-
C.
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.
-
D.
de facto head of government
A de facto head of government is a person who, regardless of formal title or legal status, effectively exercises the primary executive authority and decision-making power within a government.
-
E.
deputy head of government
A deputy head of government is a senior official who assists and can act in place of the head of government, often assuming their duties during absence, incapacity, or as delegated.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.