Triple

T11504774
Position Surface form Disambiguated ID Type / Status
Subject Kurów E272753 entity
Predicate isSeatOf P62 FINISHED
Object Gmina Kurów E929770 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 Kurów | Statement: [Kurów, isSeatOf, Gmina Kurów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Kurów
Context triple: [Kurów, isSeatOf, Gmina Kurów]
  • A. Gmina Kurów chosen
    Gmina Kurów is a rural administrative district in eastern Poland, centered on the village of Kurów in the Lublin Voivodeship.
  • B. Gmina Kurzętnik
    Gmina Kurzętnik is a rural administrative district in northern Poland, known for its agricultural landscape and small villages.
  • C. Gmina Kunów
    Gmina Kunów is an administrative district (gmina) in south-central Poland, centered on the town of Kunów within the Świętokrzyskie Voivodeship.
  • D. Gmina Korzenna
    Gmina Korzenna is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • E. Gmina Korsze
    Gmina Korsze is an administrative district (gmina) in northern Poland that encompasses the town of Korsze and surrounding villages.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d86db2f4b08190801de1b773932f59 completed April 10, 2026, 3:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6851b0f0481909d61e343b000530b completed April 20, 2026, 7:57 p.m.
Created at: April 8, 2026, 9:36 p.m.