Triple
T33095608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Arthur David Hope |
E846899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lord Justice General of Scotland |
C54785
|
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 Justice General of Scotland Context triple: [James Arthur David Hope, instanceOf, Lord Justice General of Scotland]
-
A.
Lord Chief Justice
The Lord Chief Justice is the head of the judiciary and President of the Courts of England and Wales, responsible for representing and overseeing the administration of justice within the jurisdiction.
-
B.
Lord President of the Court of Session
chosen
The Lord President of the Court of Session is the head of Scotland’s judiciary and presiding judge of its supreme civil court, responsible for overseeing the administration of justice and the conduct of the courts.
-
C.
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.
-
D.
Lord Advocate
The Lord Advocate is the chief legal officer of the Scottish Government and the Crown in Scotland, responsible for representing the government in legal matters and overseeing public prosecutions.
-
E.
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.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.