Triple

T10409721
Position Surface form Disambiguated ID Type / Status
Subject Alexander Charles Vasa E245355 entity
Predicate instanceOf P0 FINISHED
Object nobleman of the Polish–Lithuanian Commonwealth C1905 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: nobleman of the Polish–Lithuanian Commonwealth
Context triple: [Alexander Charles Vasa, instanceOf, nobleman of the Polish–Lithuanian Commonwealth]
  • A. Polish duke
    A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
  • B. Polish noblewoman
    A Polish noblewoman is a female member of the historical Polish szlachta, typically associated with landownership, social privilege, and participation in the political and cultural life of the Polish–Lithuanian Commonwealth.
  • C. nobleman chosen
    A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
  • D. Baltic German noble
    A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
  • E. 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.
  • 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_69d381be340c8190b05998703d42d224 completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 12:09 p.m.