Triple

T22058645
Position Surface form Disambiguated ID Type / Status
Subject Tarnobrzeg County E545087 entity
Predicate hasRuralGmina P46876 FINISHED
Object Gmina Gorzyce 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 Gorzyce | Statement: [Tarnobrzeg County, hasRuralGmina, Gmina Gorzyce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Gorzyce
Context triple: [Tarnobrzeg County, hasRuralGmina, Gmina Gorzyce]
  • A. Gmina Gorzyce chosen
    Gmina Gorzyce is a rural administrative district in southeastern Poland, located in the Subcarpathian Voivodeship.
  • B. Gmina Górzyca
    Gmina Górzyca is a rural administrative district in western Poland, located in the Lubusz Voivodeship near the German border.
  • C. Gmina Gorlice
    Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
  • D. Gmina Gaworzyce
    Gmina Gaworzyce is a rural administrative district in southwestern Poland, located in the Lower Silesian Voivodeship.
  • E. Gmina Góra
    Gmina Góra is an administrative district and urban-rural municipality in southwestern Poland, centered on the town of Góra in the Lower 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.