Triple

T15505173
Position Surface form Disambiguated ID Type / Status
Subject Onega River E379061 entity
Predicate tributary P415 FINISHED
Object Vyg River E1017565 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: Vyg River | Statement: [Onega River, tributary, Vyg River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vyg River
Context triple: [Onega River, tributary, Vyg River]
  • A. Vyg River chosen
    The Vyg River is a watercourse in northwestern Russia that flows through Karelia before emptying into the White Sea.
  • B. Lez River
    The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
  • C. Rees River
    The Rees River is a glacially fed river in Otago, New Zealand, flowing through the Rees Valley near Glenorchy and renowned for its scenic alpine landscapes and tramping routes.
  • D. Eno River
    The Eno River is a scenic, historically significant waterway in North Carolina known for its protected natural habitats, recreational trails, and role in the development of the Durham area.
  • E. Gavaraget River
    The Gavaraget River is a watercourse in Armenia that serves as one of the tributaries feeding into Lake Sevan.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcd5d948190b25a67a72ef980e9 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0170d8c9f0819099a398814f49f0ed completed May 11, 2026, 6:02 a.m.
Created at: April 10, 2026, 3:55 a.m.