Triple

T22227459
Position Surface form Disambiguated ID Type / Status
Subject Dukla E549379 entity
Predicate isSeatOf P62 FINISHED
Object Gmina Dukla 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 Dukla | Statement: [Dukla, isSeatOf, Gmina Dukla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Dukla
Context triple: [Dukla, isSeatOf, Gmina Dukla]
  • A. Dukla
    Dukla is a Slovak professional ice hockey club based in Trenčín, known for competing in the country’s top league and developing numerous prominent players.
  • B. Dukla chosen
    Dukla is a small historic town in southeastern Poland, near the Slovak border, known as a gateway through the Carpathian Mountains and for its role in regional trade and wartime history.
  • C. Młociny
    Młociny is a northern Warsaw neighborhood best known as the terminus of the city’s M1 metro line and a major transport hub.
  • D. Domažlice
    Domažlice is a historic town in the western Czech Republic known for its well-preserved medieval center and rich Chodové folk traditions.
  • E. Bochorna
    Bochorna is a remote highland village in the Tusheti region of northeastern Georgia, known as one of the highest permanently inhabited settlements in Europe.
  • 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_69e11e403d6481909a94d0aaf157f6ef completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12befe38c8190b547586e41b099b1 completed April 28, 2026, 9:51 p.m.
Created at: April 16, 2026, 8:37 p.m.