Triple
T32226761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph II, Holy Roman Emperor |
E823222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Member of the House of Habsburg-Lorraine |
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-Lorraine Context triple: [Joseph II, Holy Roman Emperor, instanceOf, Member of the House of Habsburg-Lorraine]
-
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 Ludovingian dynasty
A member of the Ludovingian dynasty is an individual belonging to the medieval German noble house that ruled Thuringia and held significant influence in the Holy Roman Empire from the 11th to 13th centuries.
-
C.
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.
-
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.
Luxembourg dynasty member
A Luxembourg dynasty member is an individual belonging to the medieval European royal House of Luxembourg, which produced several Holy Roman Emperors, kings, and high-ranking nobles.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:38 a.m.