Triple

T16985325
Position Surface form Disambiguated ID Type / Status
Subject Pinega River E412049 entity
Predicate hasTributary P415 FINISHED
Object Yula River E381269 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: Yula River | Statement: [Pinega River, hasTributary, Yula River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yula River
Context triple: [Pinega River, hasTributary, Yula River]
  • A. Yula River chosen
    The Yula River is a waterway in northern Russia that forms part of the drainage basin feeding into the Northern Dvina River system.
  • B. Dema River
    The Dema River is a waterway in Russia that serves as a tributary of the Belaya River within the Volga basin.
  • C. Sana River
    The Sana River is a significant river in northwestern Bosnia and Herzegovina that flows through towns such as Prijedor before joining the Una River.
  • D. Awali River
    The Awali River is a significant watercourse in Lebanon that flows through the region of Sidon before emptying into the Mediterranean Sea.
  • E. Sumène River
    The Sumène River is a watercourse in south-central France that originates in the Cantal Mountains and flows through the Auvergne region before joining larger river systems.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d18af95c8190a25ef0614e1a17f3 completed April 18, 2026, 6:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01673e1be08190b39c38fd8115a02c completed May 11, 2026, 5:21 a.m.
Created at: April 10, 2026, 5:32 a.m.