Triple

T6165921
Position Surface form Disambiguated ID Type / Status
Subject Oshpitsin E137557 entity
Predicate locatedOnRiver P165 FINISHED
Object Soła River E235567 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: Soła River | Statement: [Oshpitsin, locatedOnRiver, Soła River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Soła River
Context triple: [Oshpitsin, locatedOnRiver, Soła River]
  • A. Soła River chosen
    The Soła River is a river in southern Poland that flows through the Lesser Poland and Silesian regions before joining the Vistula.
  • B. Sopot River
    The Sopot River is a small watercourse in Montenegro that flows into the scenic Bay of Kotor on the Adriatic coast.
  • C. Łeba River
    The Łeba River is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea, passing through and feeding several coastal lakes including Lake Łebsko.
  • D. Wisłok River
    The Wisłok River is a significant river in southeastern Poland that flows through the Subcarpathian region and serves as an important tributary of the San River.
  • E. Bystrzyca River
    The Bystrzyca River is a river in eastern Poland that flows through the city of Lublin and is a tributary of the Wieprz River.
  • 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_69c008a54fc88190b6ce4416490ca79d completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d6225bc819097707be620681e7b completed March 22, 2026, 9:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6636ff608819087e25c2453220d93 completed March 27, 2026, 11:01 a.m.
Created at: March 22, 2026, 4:17 p.m.