Triple
T13247547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Burghley |
E315443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lord High Treasurer of England |
C32718
|
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: Lord High Treasurer of England Context triple: [Lord Burghley, instanceOf, Lord High Treasurer of England]
-
A.
Lord Chancellor of England
The Lord Chancellor of England was the senior official of the Crown responsible for the administration of justice, head of the judiciary, and custodian of the Great Seal, often serving as a key political advisor and high officer of state.
-
B.
Lord Chancellor
The Lord Chancellor is a senior official in the UK government historically responsible for presiding over the House of Lords, overseeing the judiciary, and serving as a key legal adviser to the Crown and government.
-
C.
Chancellor of the Exchequer (UK)
The Chancellor of the Exchequer is the UK government minister responsible for overseeing the Treasury, managing public finances, and setting economic and fiscal policy.
-
D.
clerk of the Privy Seal
A clerk of the Privy Seal was an official responsible for preparing, drafting, and processing documents that required authentication by the monarch’s privy seal, often serving as an intermediary between petitioners and higher offices of royal administration.
-
E.
Lord Marshal of England
The Lord Marshal of England was a high-ranking royal officer responsible for overseeing the king’s stables, military organization, and aspects of court ceremony and justice, particularly relating to chivalry and knighthood.
- F. None of above. chosen
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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:23 p.m.