Triple
T6012246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Reading |
E133862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lord Chief Justice of England |
C19767
|
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 Chief Justice of England Context triple: [Lord Reading, instanceOf, Lord Chief Justice 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.
Justiciar of England
The Justiciar of England was the king’s chief minister and principal royal administrator in medieval England, acting as regent in the monarch’s absence and overseeing justice, finance, and governance.
-
D.
High Steward of Scotland
The High Steward of Scotland was a hereditary noble office responsible for managing the royal household and estates, which evolved into the dynastic title held by the Stewart (later Stuart) family who became kings of Scotland and England.
-
E.
Speaker of the House of Commons of England
The Speaker of the House of Commons of England is the presiding officer responsible for maintaining order during debates, deciding who may speak, and representing the Commons to the monarch and other authorities.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:06 p.m.