Triple

T11744022
Position Surface form Disambiguated ID Type / Status
Subject Starogard Gdański E279225 entity
Predicate locatedNear P294 FINISHED
Object Tczew E277654 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: Tczew | Statement: [Starogard Gdański, locatedNear, Tczew]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tczew
Context triple: [Starogard Gdański, locatedNear, Tczew]
  • A. Tczew chosen
    Tczew is a historic town in northern Poland on the Vistula River, known for its important railway bridges and role as a regional transport hub.
  • B. Olsztynek
    Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
  • C. Kętrzyn
    Kętrzyn is a historic town in northeastern Poland known for its medieval architecture and proximity to the Masurian Lake District.
  • D. Kociewie
    Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
  • E. Choszczno
    Choszczno is a small town in northwestern Poland known for its lakes, forests, and role as a local administrative and service center.
  • 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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4f2a38c8190a682d8dae1ab9415 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff78ad38481908df2338aaf276da9 completed May 10, 2026, 3:12 a.m.
Created at: April 8, 2026, 9:41 p.m.