Triple

T16299677
Position Surface form Disambiguated ID Type / Status
Subject Port of Świnoujście E395750 entity
Predicate locatedOn P40 FINISHED
Object Świna River 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: Świna River | Statement: [Port of Świnoujście, locatedOn, Świna River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Świna River
Context triple: [Port of Świnoujście, locatedOn, Świna River]
  • A. Świna River chosen
    The Świna River is a strait in northwestern Poland that connects the Szczecin Lagoon with the Baltic Sea and separates the islands of Wolin and Usedom.
  • B. Mleczna River
    The Mleczna River is a small river in central Poland that flows through the city of Radom and forms part of its local water system.
  • C. Pełcznica River
    The Pełcznica River is a watercourse in southwestern Poland that flows through the city of Wałbrzych and its surrounding region.
  • D. Liwiec River
    The Liwiec River is a tributary of the Bug River in eastern Poland, known for its scenic, relatively unspoiled valley and importance to the surrounding rural landscapes and towns.
  • E. Pyszna River
    The Pyszna River is a small watercourse in central Poland that flows through the town of Wieluń and its surrounding region.
  • 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_69d87f23bb088190a16fbb91a1957ea5 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e25e31c9e8819094593f3aeb44f2ca completed April 17, 2026, 4:22 p.m.
Created at: April 10, 2026, 5:06 a.m.