Triple
T11736441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary of Burgundy |
E279038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Burgundian nobility |
C29728
|
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: member of the Burgundian nobility Context triple: [Mary of Burgundy, instanceOf, member of the Burgundian nobility]
-
A.
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.
-
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.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
D.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
-
E.
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.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.