Triple
T13340649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Percy, 4th Earl of Northumberland |
E317814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Percy |
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 House of Percy Context triple: [Henry Percy, 4th Earl of Northumberland, instanceOf, member of the House of Percy]
-
A.
member of the Bruce family
A member of the Bruce family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the surname Bruce.
-
B.
House of Lancaster member
A House of Lancaster member is an individual belonging to the English royal dynasty that held the throne during parts of the late Middle Ages, notably in the Wars of the Roses.
-
C.
member of the Duke family
A member of the Duke family is an individual who belongs by blood, marriage, or legal relation to the Duke lineage and participates in its shared identity, history, and social ties.
-
D.
member of the Curzon family
A member of the Curzon family is an individual belonging by birth or legal relation to the historically prominent Curzon lineage, known for its social, political, and cultural influence.
-
E.
member of the Clive family
A member of the Clive family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the Clive surname and its shared history, traditions, and relationships.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:31 p.m.