Triple
T6134687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic branch of the House of Glücksburg |
E136803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal house branch |
C14509
|
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: royal house branch Context triple: [Icelandic branch of the House of Glücksburg, instanceOf, royal house branch]
-
A.
dynastic branch
chosen
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
-
B.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
-
C.
branch of the Japanese Imperial Family
A branch of the Japanese Imperial Family is a collateral line descended from the main imperial lineage, historically established to support succession, fulfill ceremonial duties, and maintain the continuity and stability of the imperial institution.
-
D.
Scottish noble family branch
A Scottish noble family branch is a cadet line descending from a principal aristocratic house in Scotland, holding its own titles, lands, and heraldic distinctions while remaining part of the wider clan or lineage.
-
E.
Rurikid princely branch
A Rurikid princely branch is a dynastic line descending from the medieval Rurikid ruling family, typically associated with governance over a specific principality or territory in Kievan Rus’ and its successor states.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.