Triple

T5288057
Position Surface form Disambiguated ID Type / Status
Subject Busko-Zdrój E119672 entity
Predicate voivodeshipCapital P16248 FINISHED
Object Kielce E194016 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: Kielce | Statement: [Busko-Zdrój, voivodeshipCapital, Kielce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kielce
Context triple: [Busko-Zdrój, voivodeshipCapital, Kielce]
  • A. Kielce chosen
    Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
  • B. Kalisz
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • C. Tarnów
    Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
  • D. Lublin
    Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
  • E. 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.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd84db300c8190a63ac51552f0e9a6 completed March 20, 2026, 5:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9f798cbfc8190b1106298c3f211a5 completed March 30, 2026, 4:10 a.m.
Created at: March 20, 2026, 1:52 p.m.