Triple

T22644478
Position Surface form Disambiguated ID Type / Status
Subject Kozienice E558919 entity
Predicate hasNearbyCity P350 FINISHED
Object Dęblin E1042694 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: Dęblin | Statement: [Kozienice, hasNearbyCity, Dęblin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dęblin
Context triple: [Kozienice, hasNearbyCity, Dęblin]
  • A. Dęblin chosen
    Dęblin is a town in eastern Poland known for its strategic location at the confluence of major rivers and its historic military aviation school and air base.
  • B. Dębica
    Dębica is a town in southeastern Poland known as the birthplace of renowned composer and conductor Krzysztof Penderecki.
  • C. Dubno
    Dubno is a historic city in western Ukraine known for its medieval castle and role as a regional cultural and economic center.
  • D. 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.
  • E. Cieszyn
    Cieszyn is a historic town in southern Poland on the Olza River, known for its shared Polish-Czech heritage and well-preserved old town.
  • 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_69e24547f7fc819086e2c4ba3b979657 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f170366ac881909e9d1dd2e7cf7a25 completed April 29, 2026, 2:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0cdf21ac008190bc5a6fe32f4b4b50 completed May 19, 2026, 10:07 p.m.
Created at: April 17, 2026, 3:05 p.m.