Triple

T10521637
Position Surface form Disambiguated ID Type / Status
Subject Kur River E248186 entity
Predicate tributary P415 FINISHED
Object Tartar River E552475 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: Tartar River | Statement: [Kur River, tributary, Tartar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tartar River
Context triple: [Kur River, tributary, Tartar River]
  • A. Tartar River chosen
    The Tartar River is a significant watercourse in the South Caucasus that flows through parts of Azerbaijan as an important tributary within the Kura–Aras river system.
  • B. Setun River
    The Setun River is a small river in western Moscow, Russia, known as one of the city's few relatively natural waterways and a tributary of the Moskva River.
  • C. Šyša River
    The Šyša River is a small river in western Lithuania that flows into the Curonian Lagoon near the Baltic Sea coast.
  • D. Venoge River
    The Venoge River is a watercourse in the canton of Vaud in western Switzerland that flows through the Gros-de-Vaud region before emptying into Lake Geneva.
  • E. Valerik River
    The Valerik River is a waterway in the North Caucasus region of Russia, historically noted as a site of 19th-century conflicts during the Caucasian War.
  • 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_69d381c5c7448190bec34bee7ec72bac completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d509dec25881909bc748640f26a416 completed April 7, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69e623a9711081908eac4238a717305c completed April 20, 2026, 1:01 p.m.
Created at: April 6, 2026, 12:29 p.m.