Triple
T17966773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Leopoldine of Austria-Este |
E449228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Habsburg-Este |
C25390
|
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 House of Habsburg-Este Context triple: [Maria Leopoldine of Austria-Este, instanceOf, member of the House of Habsburg-Este]
-
A.
House of Habsburg member
chosen
A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
-
B.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
C.
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.
-
D.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
E.
member of the House of Karađorđević
A member of the House of Karađorđević is an individual belonging by birth or lawful adoption to the Serbian royal dynasty that historically ruled Serbia and later the Kingdom of Serbs, Croats, and Slovenes (Yugoslavia).
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:22 a.m.