Triple

T16386007
Position Surface form Disambiguated ID Type / Status
Subject Port of Elbląg E397923 entity
Predicate servesCity P82 FINISHED
Object Elbląg 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: Elbląg | Statement: [Port of Elbląg, servesCity, Elbląg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elbląg
Context triple: [Port of Elbląg, servesCity, Elbląg]
  • A. Elbląg chosen
    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.
  • B. Koszalin
    Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
  • 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. Kwidzyn
    Kwidzyn is a historic town in northern Poland known for its medieval Teutonic castle complex and Gothic cathedral.
  • E. Grójec
    Grójec is a town in east-central Poland known for its apple-growing region and proximity to Warsaw.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e3263d260081909db9ac6016d5738a completed April 18, 2026, 6:35 a.m.
Created at: April 10, 2026, 5:08 a.m.