Triple
T35896108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Percy, 4th Earl of Northumberland |
E1038228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Percy family |
C32851
|
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: member of the Percy family Context triple: [Henry Percy, 4th Earl of Northumberland, instanceOf, member of the Percy family]
-
A.
member of the House of Percy
chosen
A member of the House of Percy is an individual belonging by birth or marriage to the historic English noble family that held significant power and influence, particularly in northern England, from the medieval period onward.
-
B.
member of the Neville family
A member of the Neville family is an individual belonging by blood, marriage, or adoption to the Neville lineage, sharing its familial identity, history, and relationships.
-
C.
member of the Clifford family
A member of the Clifford family is an individual who belongs by birth, marriage, or adoption to the lineage or household identified by the Clifford surname.
-
D.
member of the Beauchamp family
A member of the Beauchamp family is an individual belonging to a historically notable lineage, often associated with nobility, heritage, and shared familial identity.
-
E.
member of the Grey family
A member of the Grey family is an individual who belongs by blood, marriage, or adoption to the lineage or household identified by the Grey surname.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.