Triple
T36245808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord William Charles Augustus Cavendick-Bentinck |
E891659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Cavendish-Bentinck family |
C19155
|
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 Cavendish-Bentinck family Context triple: [Lord William Charles Augustus Cavendick-Bentinck, instanceOf, member of the Cavendish-Bentinck family]
-
A.
member of the Cavendish family
chosen
A member of the Cavendish family is an individual belonging by birth or legal relation to the historically prominent Cavendish lineage, known for its political influence, aristocratic status, and cultural contributions.
-
B.
member of the Cecil family
A member of the Cecil family is an individual belonging to the historically influential English aristocratic lineage known for its political power, landownership, and cultural patronage.
-
C.
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.
-
D.
member of the Stanhope family
A member of the Stanhope family is an individual belonging to a specific familial lineage characterized by shared ancestry, name, and social or historical connections.
-
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.
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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.