Triple
T913368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis XVI of France |
E19714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bourbon dynasty member |
C811
|
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: Bourbon dynasty member Context triple: [Louis XVI of France, instanceOf, Bourbon dynasty member]
-
A.
member of the Kennedy family
A member of the Kennedy family is an individual belonging by birth or marriage to the prominent American political and social dynasty descended from Joseph P. Kennedy Sr. and Rose Fitzgerald Kennedy.
-
B.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
C.
member of the Darwin family
A member of the Darwin family is an individual belonging by birth or marriage to the historically notable Darwin lineage, sharing its familial ties, heritage, and social identity.
-
D.
member of the Japanese imperial family
A member of the Japanese imperial family is an individual related by blood or adoption to the Emperor of Japan, holding a formal status defined by the Imperial Household Law and participating in ceremonial, cultural, and representational duties of the monarchy.
-
E.
noble family
chosen
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.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.