Triple
T28461919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Ashley-Cooper, 10th Earl of Shaftesbury |
E720176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Shaftesbury |
C54089
|
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 Shaftesbury Context triple: [Anthony Ashley-Cooper, 10th Earl of Shaftesbury, instanceOf, Earl of Shaftesbury]
-
A.
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.
-
B.
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.
-
C.
Earl of Harewood
The Earl of Harewood is a hereditary title in the Peerage of the United Kingdom, historically associated with the Lascelles family and centered on Harewood House in Yorkshire.
-
D.
Earl of Shrewsbury
The Earl of Shrewsbury is a hereditary English noble title in the Peerage of England, historically associated with significant political influence, military leadership, and extensive landholdings, particularly in the Shropshire region.
-
E.
Earl of Leicester
The Earl of Leicester is a noble title in the Peerage of England historically granted to prominent aristocrats who held significant political, military, and social influence, particularly during the medieval and early modern periods.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:41 a.m.