Triple

T14124764
Position Surface form Disambiguated ID Type / Status
Subject Cieszyn Piasts E339999 entity
Predicate territoryIncludes P285 FINISHED
Object Bielsko 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: Bielsko | Statement: [Cieszyn Piasts, territoryIncludes, Bielsko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bielsko
Context triple: [Cieszyn Piasts, territoryIncludes, Bielsko]
  • 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. Brzesko
    Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
  • C. Bolesławiec
    Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
  • D. Zbrzyca
    Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
  • E. Kalisz
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • 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_69d81c6a95b481909e39111e0c1f31ee completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de6096976481909dc79066c5165a50 completed April 14, 2026, 3:43 p.m.
Created at: April 9, 2026, 10:22 p.m.