Triple
T36019093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Percy, 5th Earl of Northumberland |
E1041934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Northumberland |
C64912
|
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 Northumberland Context triple: [Henry Percy, 5th Earl of Northumberland, instanceOf, Earl of Northumberland]
-
A.
Earl of Cumberland
The Earl of Cumberland was an English noble title in the Peerage of England, historically associated with the Clifford family and the governance and defense of the northern border region of Cumberland.
-
B.
Earl of Northumbria
The Earl of Northumbria is a high-ranking noble title historically associated with governing the strategically important and often contested northern English region of Northumbria.
-
C.
Duke of Northumberland
The Duke of Northumberland is a hereditary noble title in the Peerage of Great Britain traditionally held by the head of the Percy family, historically one of the most powerful aristocratic dynasties in northern England.
-
D.
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.
-
E.
Earl of Chester
The Earl of Chester is a historic English noble title traditionally associated with authority over the County Palatine of Chester, often held by members of the royal family.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.