Triple
T6873264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold V, Duke of Austria |
E158604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Babenberg dynasty |
C21726
|
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 Babenberg dynasty Context triple: [Leopold V, Duke of Austria, instanceOf, member of the Babenberg dynasty]
-
A.
member of the Přemyslid dynasty
A member of the Přemyslid dynasty is an individual belonging to the medieval Czech royal house that ruled Bohemia and parts of Central Europe from the 9th to the early 14th century.
-
B.
member of the Billung dynasty
A member of the Billung dynasty is an individual belonging to the medieval German noble family that held significant ducal power in Saxony from the 10th to early 12th centuries.
-
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.
House of Hohenstaufen member
A House of Hohenstaufen member is an individual belonging to the medieval German noble dynasty that produced several Holy Roman Emperors and kings of Germany, Italy, and Sicily between the 12th and 13th centuries.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:22 p.m.