Triple

T13921534
Position Surface form Disambiguated ID Type / Status
Subject Piasts of Oświęcim E334755 entity
Predicate dynasticLegitimacy P101673 FINISHED
Object Piast royal lineage LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Piast royal lineage | Statement: [Piasts of Oświęcim, dynasticLegitimacy, Piast royal lineage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dynasticLegitimacy
Context triple: [Piasts of Oświęcim, dynasticLegitimacy, Piast royal lineage]
  • A. dynasticLegitimacyBasedOn
    Indicates that the recognized legitimacy or right to rule of a dynasty is founded upon, justified by, or derived from a specified basis or source.
  • B. dynasticLegacy
    Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
  • C. dynasticRight chosen
    Indicates a hereditary claim or entitlement to rule or hold authority based on lineage within a dynasty.
  • D. dynasticStatus
    Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
  • E. dynasticState
    Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
  • F. None of above.

Provenance (3 batches)

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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2aa5c1f481908a9d8786872f08fe completed April 14, 2026, 11:53 a.m.
PD Predicate disambiguation batch_69de059e4ba881908554f72e889719fa completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:16 p.m.