Triple

T13296163
Position Surface form Disambiguated ID Type / Status
Subject Vistula basin E316687 entity
Predicate tributary P415 FINISHED
Object Wisłoka River E801565 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: Wisłoka River | Statement: [Vistula basin, tributary, Wisłoka River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wisłoka River
Context triple: [Vistula basin, tributary, Wisłoka River]
  • A. Wisłoka River chosen
    The Wisłoka River is a river in southeastern Poland that flows through the Subcarpathian region before joining the Vistula River.
  • B. 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.
  • C. Motława River
    The Motława River is a picturesque waterway in Gdańsk, Poland, lined with historic architecture and serving as a central feature of the city’s old port and tourist district.
  • D. Włodawka River
    The Włodawka River is a small river in eastern Poland that flows through the town of Włodawa before joining the Bug River.
  • E. Iławka River
    The Iławka River is a small river in northern Poland that flows through the town of Iława and forms part of the region’s local waterway system.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99079c8508190b6208db9affcbc0e completed April 11, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69fcb6419a3c8190bfaeab65f3909474 completed May 7, 2026, 3:56 p.m.
Created at: April 9, 2026, 9:28 p.m.