Triple

T17452965
Position Surface form Disambiguated ID Type / Status
Subject Southwestern Poland E424958 entity
Predicate hasRiver P165 FINISHED
Object Nysa Kłodzka 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: Nysa Kłodzka | Statement: [Southwestern Poland, hasRiver, Nysa Kłodzka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nysa Kłodzka
Context triple: [Southwestern Poland, hasRiver, Nysa Kłodzka]
  • A. Nysa Kłodzka chosen
    Nysa Kłodzka is a river in southwestern Poland that flows through the Kłodzko Valley and Silesia before joining the Oder.
  • B. Nysa Łużycka
    Nysa Łużycka is a Central European river that forms part of the border between Germany and Poland before flowing into the Oder River.
  • C. Skawina
    Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
  • D. Krzna
    Krzna is a river in eastern Poland that flows through the Lublin region before joining the Bug River.
  • E. Skawica
    Skawica is a village in southern Poland, located in the Lesser Poland Voivodeship within the administrative district of powiat suski.
  • 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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4513faa0c8190961cf504c459bf34 completed April 19, 2026, 3:51 a.m.
Created at: April 10, 2026, 5:47 a.m.