Triple
T8125537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valdemar II of Denmark |
E189717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Estridsen |
C15721
|
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 Estridsen Context triple: [Valdemar II of Denmark, instanceOf, member of the House of Estridsen]
-
A.
member of the House of Holstein-Gottorp
A member of the House of Holstein-Gottorp is an individual belonging to a cadet branch of the Oldenburg dynasty that ruled or influenced territories in northern Germany, Scandinavia, and Russia through dynastic unions and successions.
-
B.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
-
C.
member of the House of Holstein-Gottorp-Romanov
A member of the House of Holstein-Gottorp-Romanov is an individual belonging to the German-Russian dynastic branch that ruled the Russian Empire from Peter III through the last tsars, combining Holstein-Gottorp and Romanov lineage.
-
D.
Princess of Denmark
A Princess of Denmark is a female member of the Danish royal family, typically by birth or marriage, who holds the title of princess under the Danish monarchy.
-
E.
Danish royal
chosen
A Danish royal is a member of Denmark’s monarchy, belonging to the Danish royal family by birth or marriage and typically engaged in ceremonial, constitutional, and representational duties for the Danish state.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:34 p.m.