Triple
T14137270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David of Scotland, 8th Earl of Huntingdon |
E350330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Huntingdon |
C33493
|
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: Earl of Huntingdon Context triple: [David of Scotland, 8th Earl of Huntingdon, instanceOf, Earl of Huntingdon]
-
A.
Earl of Hereford
The Earl of Hereford is a noble title in the English peerage historically granted to powerful magnates who held significant military, political, and territorial influence, particularly along the Welsh border.
-
B.
Earl of Salisbury
The Earl of Salisbury is a noble title in the Peerage of England historically held by prominent aristocratic families, often associated with significant political and military influence.
-
C.
Earl of Pembroke
The Earl of Pembroke is a noble title in the Peerage of England historically granted to powerful magnates who held significant political, military, and territorial influence, particularly in Wales and along the English–Welsh border.
-
D.
Earl of Orrery
The Earl of Orrery is a noble title in the Peerage of Ireland historically associated with the Boyle family, notably linked to political influence and the development of the mechanical model of the solar system known as an orrery.
-
E.
Earl of Suffolk
The Earl of Suffolk is a hereditary noble title in the Peerage of England historically granted to prominent aristocrats associated with the county of Suffolk, often holding significant political, military, and social influence.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:33 a.m.