Triple
T7295677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Great Chamberlain |
E164514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Great Officer of State |
C4786
|
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: Great Officer of State Context triple: [Lord Great Chamberlain, instanceOf, Great Officer of State]
-
A.
great officer of state
chosen
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.
-
B.
officer of state
An officer of state is a high-ranking public official who holds a formal position within a government or monarchy, responsible for executing specific constitutional, administrative, or ceremonial duties of the state.
-
C.
Executive Minister
An Executive Minister is a senior religious leader responsible for overseeing the administration, spiritual direction, and strategic governance of a church or denomination.
-
D.
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.
-
E.
cabinet-level government post
A cabinet-level government post is a senior executive position, typically heading a major department or ministry, that advises the head of government and helps formulate and implement national policy.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3 p.m.