Triple

T8853385
Position Surface form Disambiguated ID Type / Status
Subject Bagration Bridge (Moscow) E210691 entity
Predicate hasViewOf P854 FINISHED
Object Moscow River E14309 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: Moscow River | Statement: [Bagration Bridge (Moscow), hasViewOf, Moscow River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscow River
Context triple: [Bagration Bridge (Moscow), hasViewOf, Moscow River]
  • A. 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.
  • B. Moskva River chosen
    The Moskva River is a major waterway in western Russia that flows through and gives its name to the capital city, Moscow.
  • C. Tartar River
    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.
  • D. 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.
  • E. Ros River
    The Ros River is a significant waterway in central Ukraine that flows through the Kyiv and Cherkasy regions before joining the Dnieper 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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60c55e348190957b3bbb7397e380 completed April 1, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69d04729c39c8190a88a28288653399b completed April 3, 2026, 11:03 p.m.
Created at: March 30, 2026, 6:49 p.m.