Triple

T11744023
Position Surface form Disambiguated ID Type / Status
Subject Starogard Gdański E279225 entity
Predicate locatedNear P294 FINISHED
Object Gdańsk E18213 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: Gdańsk | Statement: [Starogard Gdański, locatedNear, Gdańsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gdańsk
Context triple: [Starogard Gdański, locatedNear, Gdańsk]
  • A. Gdańsk chosen
    Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
  • B. Gdynia
    Gdynia is a major seaport city on Poland’s Baltic coast, developed rapidly in the 20th century into one of the country’s key maritime and economic centers.
  • C. Bydgoszcz
    Bydgoszcz is a major city in northern Poland known as an important economic, cultural, and academic center on the Brda and Vistula rivers.
  • D. Szczecin
    Szczecin is a large Polish city and important maritime and industrial center in northwestern Poland, situated near the Baltic Sea and the German border.
  • E. Koszalin
    Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic 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_69f63449892881909d361815cbfcdee5 completed May 2, 2026, 5:28 p.m.
Created at: April 8, 2026, 9:41 p.m.