Triple
T16209758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir James Eyre |
E393428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chief Baron of the Exchequer |
C37127
|
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: Chief Baron of the Exchequer Context triple: [Sir James Eyre, instanceOf, Chief Baron of the Exchequer]
-
A.
Lord High Treasurer of England
The Lord High Treasurer of England was the senior royal official responsible for overseeing the kingdom’s finances, revenue collection, and fiscal administration.
-
B.
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.
-
C.
Lord Chief Justice of England
The Lord Chief Justice of England is the head of the judiciary and president of the Courts of England and Wales, responsible for overseeing the administration of justice and representing the views of the judiciary to Parliament and the government.
-
D.
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.
-
E.
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.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:03 a.m.