Triple
T15040184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnus Minnesköld |
E378578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Bjelbo |
C34698
|
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 Bjelbo Context triple: [Magnus Minnesköld, instanceOf, member of the House of Bjelbo]
-
A.
member of the Nemanjić dynasty
A member of the Nemanjić dynasty is an individual belonging to the medieval Serbian royal family that ruled Serbia from the late 12th to the mid-14th century, shaping its political, cultural, and religious development.
-
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.
member of the House of Karađorđević
A member of the House of Karađorđević is an individual belonging by birth or lawful adoption to the Serbian royal dynasty that historically ruled Serbia and later the Kingdom of Serbs, Croats, and Slovenes (Yugoslavia).
-
D.
member of the House of Alpin
A member of the House of Alpin is an individual belonging to the early medieval royal dynasty that ruled the Kingdom of the Picts and later the unified Kingdom of Scotland from the 9th to the 11th centuries.
-
E.
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.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.