Triple

T8761860
Position Surface form Disambiguated ID Type / Status
Subject Soła Oświęcim E208220 entity
Predicate namedAfter P63 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: [Soła Oświęcim, namedAfter, Soła River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Soła River
Context triple: [Soła Oświęcim, namedAfter, 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. Elbląg River
    The Elbląg River is a river in northern Poland that flows through the city of Elbląg and connects inland waterways with the Vistula Lagoon and the Baltic Sea.
  • D. Ł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.
  • E. 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.
  • 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_69ca835df7e08190ac875664cca8f9ca completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5dfa9d6c81908c4c6b3a6f84f67d completed March 31, 2026, 11:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69d017060fd08190bd053f988bd74048 completed April 3, 2026, 7:37 p.m.
Created at: March 30, 2026, 6:40 p.m.