Triple

T13917655
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Terek River E334663 entity
Predicate location P40 FINISHED
Object Terek River E101178 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: Terek River | Statement: [Battle of the Terek River, location, Terek River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Terek River
Context triple: [Battle of the Terek River, location, Terek River]
  • A. Terek River chosen
    The Terek River is a major river in the North Caucasus that flows through Georgia and Russia before emptying into the Caspian Sea.
  • B. Irtysh River
    The Irtysh River is a major river in Central Asia and Western Siberia that flows through China, Kazakhstan, and Russia before joining the Ob River.
  • C. Taimyr River
    The Taimyr River is a remote Arctic river in northern Siberia, Russia, flowing across the Taimyr Peninsula into the Kara Sea.
  • D. Amu River
    The Amu River, historically known as the Oxus, is a major Central Asian river that flows from the Pamir Mountains toward the Aral Sea and has long served as an important cultural and political boundary in the region.
  • E. Tuman River
    The Tuman River is a border river in Northeast Asia that flows between China, North Korea, and Russia before emptying into the Sea of Japan.
  • 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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de272753e48190bc609482635280ff completed April 14, 2026, 11:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003c405ecc81909722377a22db84a5 completed May 10, 2026, 8:05 a.m.
Created at: April 9, 2026, 10:16 p.m.