Triple
T24372511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curzon of Kedleston |
E614373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of House of Curzon |
C48391
|
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: branch of House of Curzon Context triple: [Curzon of Kedleston, instanceOf, branch of House of Curzon]
-
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 House of Spencer-Churchill
A member of the House of Spencer-Churchill is an individual belonging by birth or lawful descent to the aristocratic British family formed by the union of the Spencer and Churchill lineages.
-
C.
member of the House of Battenberg
A member of the House of Battenberg is an individual belonging by birth or legitimate descent to the morganatic German princely family that later anglicized its name to Mountbatten and became closely connected to the British royal family.
-
D.
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.
-
E.
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.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:02 a.m.