Triple
T1563392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold II, Holy Roman Emperor |
E33377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Habsburg-Lorraine |
C6219
|
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-Lorraine Context triple: [Leopold II, Holy Roman Emperor, instanceOf, member of the House of Habsburg-Lorraine]
-
A.
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.
-
B.
Habsburg monarch
chosen
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
C.
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.
-
D.
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.
-
E.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.