Triple

T22290167
Position Surface form Disambiguated ID Type / Status
Subject Gmina Chrzanów E550972 entity
Predicate borderedBy P224 FINISHED
Object Gmina Trzebinia 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 Trzebinia | Statement: [Gmina Chrzanów, borderedBy, Gmina Trzebinia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Trzebinia
Context triple: [Gmina Chrzanów, borderedBy, Gmina Trzebinia]
  • A. Gmina Trzebinia chosen
    Gmina Trzebinia is an urban-rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • B. Gmina Trzebownisko
    Gmina Trzebownisko is a rural administrative district in southeastern Poland, situated near the city of Rzeszów in the Subcarpathian Voivodeship.
  • C. Gmina Trawniki
    Gmina Trawniki is a rural administrative district in eastern Poland that includes the village of Trawniki and surrounding settlements.
  • D. Gmina Trzciana
    Gmina Trzciana is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • E. Gmina Gubin
    Gmina Gubin is a rural administrative district in western Poland, situated in Lubusz Voivodeship near the German border.
  • 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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560adde88190961d8fc24c1c4b3c completed April 29, 2026, 12:51 a.m.
Created at: April 16, 2026, 8:41 p.m.