Triple
T35315518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinando Stanhope |
E1019893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Stanhope family |
C64776
|
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 Stanhope family Context triple: [Ferdinando Stanhope, instanceOf, member of the Stanhope family]
-
A.
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.
-
B.
member of the Grosvenor family
A member of the Grosvenor family is an individual belonging by birth or legal relation to the historically prominent British aristocratic lineage associated with substantial landholdings and the title of Duke of Westminster.
-
C.
member of the Montagu family
A member of the Montagu family is an individual belonging by birth or legal relation to the historically prominent Montagu lineage, known for its social, political, and cultural influence.
-
D.
member of the Stanley family
A member of the Stanley family is an individual who belongs by birth, marriage, or adoption to the familial group identified by the shared Stanley surname and its associated relationships, traditions, and lineage.
-
E.
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.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.