Triple
T6733738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neapolitan Bourbons |
E153701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cadet branch of the House of Bourbon |
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: cadet branch of the House of Bourbon Context triple: [Neapolitan Bourbons, instanceOf, cadet branch of the House of Bourbon]
-
A.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
-
B.
member of the House of Valois
A member of the House of Valois is an individual belonging to the French royal dynasty that ruled France and several related territories from the 14th to the 16th centuries.
-
C.
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.
-
D.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
E.
branch of the Japanese Imperial Family
A branch of the Japanese Imperial Family is a collateral line descended from the main imperial lineage, historically established to support succession, fulfill ceremonial duties, and maintain the continuity and stability of the imperial institution.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:09 p.m.