Triple

T18125868
Position Surface form Disambiguated ID Type / Status
Subject Świnoujście E433872 entity
Predicate locatedAtMouthOf P165 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: [Świnoujście, locatedAtMouthOf, Świna River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Świna River
Context triple: [Świnoujście, locatedAtMouthOf, Ś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. Świnka River
    The Świnka River is a small river in eastern Poland that flows through the town of Łęczna and forms part of the local drainage system of the Lublin region.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddee1efc8190b04324b98de5c9d0 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:29 a.m.