Triple
T25682488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry II, Duke of Austria |
E643977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Babenberg |
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 House of Babenberg Context triple: [Henry II, Duke of Austria, instanceOf, member of the House of Babenberg]
-
A.
member of the Babenberg dynasty
chosen
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.
-
B.
member of the House of Kyburg
A member of the House of Kyburg is an individual belonging to the medieval Swiss noble dynasty that held significant territorial and political power in parts of present-day Switzerland during the High Middle Ages.
-
C.
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.
-
D.
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.
-
E.
member of the Árpád dynasty
A member of the Árpád dynasty is an individual belonging to the medieval Hungarian royal house that ruled the Kingdom of Hungary and its predecessor entities from the late 9th century until 1301.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:02 p.m.