Triple
T27976686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADM (Policy) |
E706508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior government official role |
C8786
|
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: senior government official role Context triple: [ADM (Policy), instanceOf, senior government official role]
-
A.
senior civil servant role
A senior civil servant role is a high-level government position responsible for providing strategic leadership, policy advice, and oversight of public administration to ensure effective implementation of governmental objectives.
-
B.
public official role
chosen
A public official role is a position of authority or responsibility within government or public institutions, empowered to make or influence decisions that affect the public interest.
-
C.
senior United Nations position
A senior United Nations position is a high-level leadership role responsible for shaping and implementing UN policies, strategies, and operations across member states and agencies.
-
D.
great officer of state
A great officer of state is a high-ranking official who holds one of the most senior ceremonial or executive positions within a government or royal household, often with historic and constitutional significance.
-
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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:41 p.m.