Triple

T17425803
Position Surface form Disambiguated ID Type / Status
Subject Brzeżany Castle E423733 entity
Predicate ownedBy P347 FINISHED
Object Sieniawski family NE NERFINISHED

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: Sieniawski family | Statement: [Brzeżany Castle, ownedBy, Sieniawski family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sieniawski family
Context triple: [Brzeżany Castle, ownedBy, Sieniawski family]
  • A. Sieniawski family chosen
    The Sieniawski family was a powerful Polish noble lineage that held high offices and extensive estates in the Polish–Lithuanian Commonwealth.
  • B. Sienieński family
    The Sienieński family was a Polish noble lineage best known for establishing the town of Raków, an important center of the Polish Reformation.
  • C. Krasnowolski family
    The Krasnowolski family is a Polish noble lineage historically associated with the Radwan heraldic clan.
  • D. Kraszewski family
    The Kraszewski family is a Polish noble lineage historically associated with the Radwan coat of arms.
  • E. Żółkiewski family
    The Żółkiewski family was a prominent Polish noble (szlachta) lineage of the Polish–Lithuanian Commonwealth, best known for producing the distinguished military commander and statesman Stanisław Żółkiewski.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e448fbfda88190be1c001d64289bf7 completed April 19, 2026, 3:16 a.m.
Created at: April 10, 2026, 5:46 a.m.