Triple

T34233940
Position Surface form Disambiguated ID Type / Status
Subject Oder–Neisse river system E878279 entity
Predicate hasOutflowThrough P159234 FINISHED
Object Pomeranian Bay 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: Pomeranian Bay | Statement: [Oder–Neisse river system, hasOutflowThrough, Pomeranian Bay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOutflowThrough
Context triple: [Oder–Neisse river system, hasOutflowThrough, Pomeranian Bay]
  • A. isNaturalOutletOf
    Indicates that one water body or channel serves as the primary natural discharge path through which another water body releases its water.
  • B. flowsUltimatelyInto chosen
    Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
  • C. outflow
    Indicates the movement or discharge of something from an origin or source to the outside or to another location.
  • D. flowsFrom
    Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
  • E. flowsAt
    Indicates that a fluid or substance moves through or along a specific location, point, or region.
  • F. None of above.

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_69f349b22d8c819096b22df268382aa9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f728a345488190bd7e6751b09ac591 completed May 3, 2026, 10:51 a.m.
PD Predicate disambiguation batch_69f7283ef2608190a7a85d7e7f5332c0 completed May 3, 2026, 10:49 a.m.
Created at: May 1, 2026, 1:56 a.m.