Triple
T28641988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Henry Wellesley, 2nd Earl Cowley |
E724951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Wellesley family |
C54376
|
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 Wellesley family Context triple: [William Henry Wellesley, 2nd Earl Cowley, instanceOf, member of the Wellesley family]
-
A.
member of the Mitford family
A member of the Mitford family is an individual belonging by birth or marriage to the historically notable English Mitford clan, known for its aristocratic background and politically and socially prominent siblings.
-
B.
member of the Winthrop family
A member of the Winthrop family is an individual belonging by birth, marriage, or adoption to the historically prominent Winthrop lineage, sharing its familial identity, heritage, and social ties.
-
C.
member of the Spencer family
A member of the Spencer family is an individual who belongs by birth, marriage, or legal relation to the Spencer lineage, sharing its familial identity, heritage, and social ties.
-
D.
member of the Mitford family circle
A member of the Mitford family circle is an individual who belongs to, is related to, or is closely associated with the Mitford sisters and their extended social, political, and literary milieu in early- to mid-20th-century Britain.
-
E.
member of the Fairfax family
A member of the Fairfax family is an individual who belongs by blood, marriage, or legal adoption to the Fairfax lineage and participates in its shared identity, history, 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:45 a.m.