Triple

T11874400
Position Surface form Disambiguated ID Type / Status
Subject Popowo, Poland E282487 entity
Predicate administrativeDistrict P2709 FINISHED
Object Gmina Łubowo E950658 NE 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: Gmina Łubowo | Statement: [Popowo, Poland, administrativeDistrict, Gmina Łubowo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Łubowo
Context triple: [Popowo, Poland, administrativeDistrict, Gmina Łubowo]
  • A. Gmina Łubowo chosen
    Gmina Łubowo is a rural administrative district in west-central Poland, situated in the Greater Poland Voivodeship and known for its villages and agricultural character.
  • B. Gmina Łubnice
    Gmina Łubnice is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
  • C. Gmina Lubień
    Gmina Lubień is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • D. Gmina Łącko
    Gmina Łącko is a rural administrative district in southern Poland, known for its picturesque mountainous landscapes and traditional highland culture.
  • E. Gmina Łużna
    Gmina Łużna is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8be1a22448190bd0722188c14d7bd completed April 10, 2026, 9:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69f417cb1c3881909ee50e8d11621664 completed May 1, 2026, 3:02 a.m.
Created at: April 8, 2026, 9:44 p.m.