Triple
T17602614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohan-Soubise branch |
E428740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French noble family branch |
C39418
|
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: French noble family branch Context triple: [Rohan-Soubise branch, instanceOf, French noble family branch]
-
A.
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.
-
B.
French political dynasty
A French political dynasty is a family whose members, across multiple generations, hold significant political power and influence within France’s governmental and public institutions.
-
C.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
-
D.
Occitan noble family
An Occitan noble family is a lineage of aristocratic households originating from the historical Occitania region in southern Europe, distinguished by hereditary titles, landholdings, and regional cultural influence.
-
E.
medieval French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.