Triple

T10128878
Position Surface form Disambiguated ID Type / Status
Subject Karachayevsk E226283 entity
Predicate locatedOnRiver P165 FINISHED
Object Teberda River E329363 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: Teberda River | Statement: [Karachayevsk, locatedOnRiver, Teberda River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teberda River
Context triple: [Karachayevsk, locatedOnRiver, Teberda River]
  • A. Teberda River chosen
    The Teberda River is a mountain river in the North Caucasus region of Russia that flows through the Teberda Nature Reserve before joining the Kuban River.
  • B. Selemdzha River
    The Selemdzha River is a significant river in Russia’s Amur Oblast, known for its remote taiga landscapes and role in the regional hydrological system.
  • C. Bega River
    The Bega River is a waterway in southeastern New South Wales, Australia, that flows through the town of Bega before reaching the Tasman Sea.
  • D. Sajna River
    The Sajna River is a small river in northern Poland that flows through the town of Reszel in the Warmian-Masurian region.
  • E. Hrazdan River
    The Hrazdan River is a significant waterway in Armenia that flows from Lake Sevan through the capital city of Yerevan before joining the Aras 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd333186c819088bbf617967f24fa completed April 2, 2026, 2:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69e4963545f481909ecc360480b1fc37 completed April 19, 2026, 8:45 a.m.
Created at: March 30, 2026, 9:05 p.m.