Triple
T34297415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Spencer |
E880069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viscount Althorp |
C27548
|
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: Viscount Althorp Context triple: [Lord Spencer, instanceOf, Viscount Althorp]
-
A.
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.
-
B.
Duke of Devonshire
The Duke of Devonshire is a hereditary noble title in the Peerage of England, traditionally held by the head of the Cavendish family, historically influential in British politics, society, and the stewardship of estates such as Chatsworth House.
-
C.
Viscount FitzWilliam
chosen
Viscount FitzWilliam is a noble title in the British peerage historically associated with the FitzWilliam family, often denoting a hereditary aristocrat with social, political, and landholding influence.
-
D.
Earl of Shaftesbury
The Earl of Shaftesbury is a hereditary noble title in the Peerage of England, historically associated with influential political, philosophical, and social reform figures from the Ashley-Cooper family.
-
E.
Earl of Arundel
The Earl of Arundel is a noble title in the English peerage historically associated with the lordship of Arundel Castle and often linked to the premier earldom of England.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.