Triple

T13441825
Position Surface form Disambiguated ID Type / Status
Subject Balice E320379 entity
Predicate hasNameInLanguage P15 FINISHED
Object Balice (Polish) E320379 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: Balice (Polish) | Statement: [Balice, hasNameInLanguage, Balice (Polish)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balice (Polish)
Context triple: [Balice, hasNameInLanguage, Balice (Polish)]
  • A. Bałucianka
    Bałucianka is a village in southeastern Poland, situated in the Subcarpathian region and administered as part of Gmina Rymanów.
  • B. Błonie (Polish)
    Błonie (Polish) is a town in east-central Poland, located west of Warsaw, known historically as part of the former Congress Poland.
  • C. Balice chosen
    Balice is a village near Kraków in southern Poland, best known for hosting the region’s main international airport.
  • D. Bystrzyca (Polish)
    Bystrzyca is a river in southwestern Poland that flows through the Sudetes and the city of Wrocław before joining the Oder River.
  • E. Bzura (Polish)
    Bzura (Polish) is the Polish name of the Bzura River, a tributary of the Vistula in central Poland known for its historical significance, including battles during World War II.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee704ac8190b4c7f4e0d3a88494 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7399421908190a7750e37c89a73f6 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:40 p.m.