Triple

T12235978
Position Surface form Disambiguated ID Type / Status
Subject Kociewie E291592 entity
Predicate hasCapital P204 FINISHED
Object Starogard Gdański E279225 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: Starogard Gdański | Statement: [Kociewie, hasCapital, Starogard Gdański]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Starogard Gdański
Context triple: [Kociewie, hasCapital, Starogard Gdański]
  • A. Starogard Gdański chosen
    Starogard Gdański is a historic town in northern Poland that serves as an important local industrial and cultural center in the Kociewie region.
  • B. Gryfice
    Gryfice is a historic town in northwestern Poland known for its medieval urban layout and remnants of defensive walls.
  • C. Kwidzyn
    Kwidzyn is a historic town in northern Poland known for its medieval Teutonic castle complex and Gothic cathedral.
  • D. Giżycko
    Giżycko is a popular lakeside town in northeastern Poland, known as a major sailing and tourism center in the Masurian Lake District.
  • E. Elbląg
    Elbląg is a historic city in northern Poland known for its reconstructed Old Town, medieval heritage, and role as an important port and industrial 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb2892c81909a97b3ad6ec2c21b completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f739668f3481909cc7564c3ede2896 completed May 3, 2026, 12:02 p.m.
Created at: April 8, 2026, 9:51 p.m.