Triple

T2919450
Position Surface form Disambiguated ID Type / Status
Subject Greater Poland Voivodeship E78683 entity
Predicate containsCity P294 FINISHED
Object Kalisz E133882 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: Kalisz | Statement: [Greater Poland Voivodeship, containsCity, Kalisz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalisz
Context triple: [Greater Poland Voivodeship, containsCity, Kalisz]
  • A. Kalisz chosen
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • B. Kielce
    Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
  • C. Bielsko-Biała
    Bielsko-Biała is a city in southern Poland at the foot of the Beskid Mountains, known as a regional industrial and cultural center formed from the historic towns of Bielsko and Biała.
  • D. Tarnów
    Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
  • E. Suwałki
    Suwałki is a city in northeastern Poland known for its cold climate, proximity to the Lithuanian border, and location within the historical region of Podlasie.
  • 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_69ad8b0c2ad081909ff87050ae542bb9 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad96a53f8c8190b188d549f1161e84 completed March 8, 2026, 3:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69beef70e6048190b0e5659a59634d5d completed March 21, 2026, 7:20 p.m.
Created at: March 8, 2026, 2:54 p.m.