Triple
T17738837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Hamilton, 5th Duke of Abercorn |
E442796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Hamilton |
C39616
|
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 Hamilton Context triple: [James Hamilton, 5th Duke of Abercorn, instanceOf, member of the House of Hamilton]
-
A.
member of the Stewart family
A member of the Stewart family is an individual who belongs by birth, marriage, or legal relation to the familial group identified by the Stewart surname and its shared lineage, traditions, and relationships.
-
B.
member of the Livingston family
A member of the Livingston family is an individual who belongs by birth, marriage, or legal adoption to the historically prominent Livingston lineage, sharing its familial identity, heritage, and social ties.
-
C.
member of the House of Alba
A member of the House of Alba is an individual belonging by birth or marriage to the historic Spanish noble family renowned for its extensive titles, estates, and cultural influence.
-
D.
member of the Washington family
A member of the Washington family is an individual who belongs by blood, marriage, or legal relation to the historically notable Washington lineage, including but not limited to the family of George Washington.
-
E.
member of the Herbert family
A member of the Herbert family is an individual who belongs by birth, marriage, or adoption to the Herbert lineage and participates in its shared relationships, traditions, and identity.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:09 a.m.