Triple

T15941560
Position Surface form Disambiguated ID Type / Status
Subject Mezen River E386575 entity
Predicate tributary P415 FINISHED
Object Sula River 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: Sula River | Statement: [Mezen River, tributary, Sula River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sula River
Context triple: [Mezen River, tributary, Sula River]
  • A. Sula River
    The Sula River is a significant tributary of the Dnieper River in central Ukraine, known for its role in regional ecology, agriculture, and settlements.
  • B. Sula River chosen
    The Sula River is a waterway in northern European Russia that forms part of the Pechora River basin within the Arctic drainage system.
  • C. Sil River
    The Sil River is a major waterway in northwestern Spain that flows through mountainous landscapes, including the Province of León, and is known for its deep canyons and hydroelectric use.
  • D. You River
    The You River is a tributary waterway in southern China that feeds into the larger Yuan River system.
  • E. Neches River
    The Neches River is a major waterway in eastern Texas that flows from near Tyler to the Gulf of Mexico, supporting regional ecosystems, industry, and recreation.
  • 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_69d86da750008190987eb26be3f6c118 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156ce0230819089a20114a755a75a completed April 16, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:53 a.m.