Triple

T22058639
Position Surface form Disambiguated ID Type / Status
Subject Tarnobrzeg County E545087 entity
Predicate contains P35 FINISHED
Object Gmina Wilczyce 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: Gmina Wilczyce | Statement: [Tarnobrzeg County, contains, Gmina Wilczyce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Wilczyce
Context triple: [Tarnobrzeg County, contains, Gmina Wilczyce]
  • A. Gmina Wilczyce chosen
    Gmina Wilczyce is a rural administrative district in south-eastern Poland, located in the Świętokrzyskie Voivodeship.
  • B. Gmina Wilczęta
    Gmina Wilczęta is a rural administrative district in northern Poland, known for its small villages and forested landscapes within the Warmian-Masurian Voivodeship.
  • C. Gmina Wiśniowa
    Gmina Wiśniowa is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • D. Gmina Wiślica
    Gmina Wiślica is a rural administrative district in south-central Poland, centered on the historic town of Wiślica and located within the Świętokrzyskie Voivodeship.
  • E. Gmina Wyry
    Gmina Wyry is a rural administrative district in southern Poland, located within the Silesian Voivodeship.
  • 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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285959f48190b89527b3f9e7ab11 completed April 28, 2026, 9:36 p.m.
Created at: April 16, 2026, 8:27 p.m.