Triple

T21914723
Position Surface form Disambiguated ID Type / Status
Subject Gmina Łoniów E541154 entity
Predicate administrativeCenter P1474 FINISHED
Object Łoniów 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: Łoniów | Statement: [Gmina Łoniów, administrativeCenter, Łoniów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Łoniów
Context triple: [Gmina Łoniów, administrativeCenter, Łoniów]
  • A. Łoniów chosen
    Łoniów is a village in south-eastern Poland that serves as the seat of the rural administrative district (gmina) of Łoniów in Sandomierz County, Świętokrzyskie Voivodeship.
  • B. Goleniów
    Goleniów is a town in northwestern Poland that serves as a local transport hub and gateway to the nearby regional capital Szczecin.
  • C. Wolyniec
    Wolyniec is a Polish-origin surname most notably associated with American soccer player and coach John Wolyniec.
  • D. Wawrzeńczyce
    Wawrzeńczyce is a village in southern Poland that serves as the administrative center of the rural Gmina Igołomia-Wawrzeńczyce in Lesser Poland Voivodeship.
  • E. Łęczna
    Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
  • 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_69e0c47c4b9c8190a5586a75f5f36453 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f123366cb88190a42aa741e1245fd9 completed April 28, 2026, 9:14 p.m.
Created at: April 16, 2026, 7:42 p.m.