Triple
T9034295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algernon Percy, 6th Duke of Northumberland |
E216451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Northumberland |
C25500
|
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: Duke of Northumberland Context triple: [Algernon Percy, 6th Duke of Northumberland, instanceOf, Duke of Northumberland]
-
A.
Earl of Lancaster
The Earl of Lancaster was a prominent English noble title, often held by close relatives of the king, associated with extensive lands, political influence, and a key role in medieval English governance and conflicts.
-
B.
Duke of Lancaster
The Duke of Lancaster is a noble title in the Peerage of England historically associated with the ruling monarch and the administration of the Duchy of Lancaster, a royal estate providing independent income to the sovereign.
-
C.
Earl of Derby
The Earl of Derby is a hereditary title in the Peerage of England, historically associated with the influential Stanley family, whose holders have played prominent political and social roles since the late Middle Ages.
-
D.
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.
-
E.
Duke of Richmond
The Duke of Richmond is a hereditary noble title in the Peerage of England, historically granted to members of the royal family or high-ranking aristocrats associated with the region of Richmond.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:08 p.m.