Triple

T19419059
Position Surface form Disambiguated ID Type / Status
Subject Bolshaya Polyanka Street area E485796 entity
Predicate near P350 FINISHED
Object Moscow River NE NERFINISHED

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: [Bolshaya Polyanka Street area, near, Moscow River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscow River
Context triple: [Bolshaya Polyanka Street area, near, 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. Miass River
    The Miass River is a waterway in the southern Ural region of Russia that flows through the industrial city of Chelyabinsk before joining the Iset River.
  • D. 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.
  • E. Yashchera River
    The Yashchera River is a smaller watercourse in northwestern Russia that serves as a tributary within the Luga River basin.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62afbaf0c8190913eda4b04efbe67 completed April 20, 2026, 1:32 p.m.
Created at: April 10, 2026, 1:37 p.m.