Triple

T13764626
Position Surface form Disambiguated ID Type / Status
Subject Elbląg E330705 entity
Predicate hasPort P35 FINISHED
Object Port of Elbląg E397923 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: Port of Elbląg | Statement: [Elbląg, hasPort, Port of Elbląg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Elbląg
Context triple: [Elbląg, hasPort, Port of Elbląg]
  • A. Port of Elbląg chosen
    The Port of Elbląg is a regional seaport and transport hub on the Elbląg River near the Vistula Lagoon, serving cargo, passenger, and recreational traffic in northern Poland.
  • B. Port of Gdańsk
    The Port of Gdańsk is one of Poland’s largest and most important seaports on the Baltic Sea, serving as a major hub for international trade and maritime transport.
  • C. Port of Szczecin
    The Port of Szczecin is a major Polish seaport on the Oder River near the Baltic Sea, serving as an important hub for maritime trade and inland waterway transport in northwestern Poland.
  • D. Port of Gdynia
    The Port of Gdynia is a major seaport on Poland’s Baltic coast, serving as a key hub for maritime trade, passenger traffic, and naval activity.
  • E. Port of Świnoujście
    The Port of Świnoujście is a key Baltic Sea seaport and ferry terminal in northwestern Poland, serving both commercial shipping and passenger traffic.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de022690ac8190bd5410ecc659a2a7 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a862e6808190b8fbb27304212058 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:10 p.m.