Triple
T13762684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haakon the Young |
E330652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Norwegian noble |
C19839
|
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: medieval Norwegian noble Context triple: [Haakon the Young, instanceOf, medieval Norwegian noble]
-
A.
Norwegian noble
chosen
A Norwegian noble is a member of the historical aristocratic class in Norway, traditionally holding hereditary titles, land, and social privileges within the Norwegian realm.
-
B.
Danish noble
A Danish noble is a member of Denmark’s hereditary aristocracy, historically granted titles, privileges, and land in exchange for loyalty and service to the crown.
-
C.
Swedish noble
A Swedish noble is a member of Sweden’s historically privileged aristocratic estate, traditionally holding hereditary titles, social status, and often land or political influence within the Swedish realm.
-
D.
medieval European noble
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
E.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:10 p.m.