Triple
T7612584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbon (by marriage) |
E172278
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | noble house membership by marriage |
C22601
|
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: noble house membership by marriage Context triple: [Bourbon (by marriage), instanceOf, noble house membership by marriage]
-
A.
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.
-
B.
Nobility
Nobility is a social class traditionally distinguished by hereditary titles, privileges, and elevated status, often associated with land ownership, political influence, and cultural prestige.
-
C.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
-
D.
system of nobility
A system of nobility is a hierarchical social structure in which hereditary or granted titles confer formal ranks, privileges, and obligations within a society.
-
E.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:55 p.m.