Triple

T3508547
Position Surface form Disambiguated ID Type / Status
Subject Wolfsburg E74139 entity
Predicate twinCity P1072 FINISHED
Object Bielsko-Biała E90431 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: Bielsko-Biała | Statement: [Wolfsburg, twinCity, Bielsko-Biała]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bielsko-Biała
Context triple: [Wolfsburg, twinCity, Bielsko-Biała]
  • A. Bielsko-Biała chosen
    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.
  • 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. Hrubieszów
    Hrubieszów is a historic town in eastern Poland near the Ukrainian border, known for its multicultural heritage and location in the Lublin region.
  • D. Kielce
    Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
  • E. Zabrze
    Zabrze is an industrial city in the Silesian region of southern Poland, historically known for coal mining and heavy industry.
  • 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc0cc394819087a9b598023f4f93 completed March 8, 2026, 6:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfc60426248190947e1c58fe4dd1b1 completed March 22, 2026, 10:35 a.m.
Created at: March 8, 2026, 3:18 p.m.