Triple
T18511925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert de Clifford, 1st Baron de Clifford |
E452362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lord Warden of the Marches |
C40524
|
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 Warden of the Marches Context triple: [Robert de Clifford, 1st Baron de Clifford, instanceOf, Lord Warden of the Marches]
-
A.
Third Marshal of the Riddermark
The Third Marshal of the Riddermark is a high-ranking Rohirrim military commander responsible for leading one of Rohan’s primary field armies and defending a designated region of the Riddermark.
-
B.
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.
-
C.
Lord High Constable of England
The Lord High Constable of England was one of the great officers of state, historically responsible for commanding the royal armies, overseeing matters of chivalry and knighthood, and presiding over the Court of Chivalry.
-
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.
Kingsguard knight
A Kingsguard knight is an elite, oath-bound royal bodyguard sworn to protect the king and royal family with unwavering loyalty, martial prowess, and lifelong service.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:36 a.m.