Triple
T8635194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles the Rash |
E204506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Valois-Burgundy member |
C9376
|
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: House of Valois-Burgundy member Context triple: [Charles the Rash, instanceOf, House of Valois-Burgundy member]
-
A.
member of the House of Valois
chosen
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.
-
B.
House of Lorraine member
A House of Lorraine member is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled Lorraine and later provided emperors, kings, and consorts to several major monarchies.
-
C.
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.
-
D.
House of Wittelsbach member
A House of Wittelsbach member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories such as Bavaria and the Palatinate and provided various European kings and emperors.
-
E.
member of the House of Lorraine
A member of the House of Lorraine is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled the Duchy of Lorraine and later held significant royal and imperial titles.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.