Triple

T15815288
Position Surface form Disambiguated ID Type / Status
Subject Benedict Birgersson E383458 entity
Predicate instanceOf P0 FINISHED
Object medieval Swedish nobleman C12951 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 Swedish nobleman
Context triple: [Benedict Birgersson, instanceOf, medieval Swedish nobleman]
  • A. Swedish noble chosen
    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.
  • B. 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.
  • C. Finnish nobleman
    A Finnish nobleman is a male member of Finland’s historical nobility, typically holding hereditary titles, land, and social status recognized under the Swedish and later Russian rule, and often involved in military, administrative, or political leadership.
  • D. 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.
  • E. 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.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:49 a.m.