Triple
T33052109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccleuch branch |
E845753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aristocratic family branch |
C14509
|
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: aristocratic family branch Context triple: [Buccleuch branch, instanceOf, aristocratic family branch]
-
A.
dynastic branch
chosen
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
-
B.
noble family
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
C.
French noble family branch
A French noble family branch is a distinct lineage descending from a common aristocratic ancestor, recognized by its own title, estates, and heraldic identity within the broader noble house.
-
D.
German noble family branch
A German noble family branch is a distinct lineage or subdivision of a larger aristocratic house in German-speaking regions, typically defined by shared ancestry, territorial holdings, and hereditary titles.
-
E.
branch of the British royal family
A branch of the British royal family is a distinct lineage descending from a particular monarch or royal ancestor, recognized as part of the wider royal house and often associated with specific titles, roles, and estates.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.