Triple

T16289652
Position Surface form Disambiguated ID Type / Status
Subject Moscow Ring of waterways E395484 entity
Predicate hasPart P35 FINISHED
Object Yauza River E104708 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: Yauza River | Statement: [Moscow Ring of waterways, hasPart, Yauza River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yauza River
Context triple: [Moscow Ring of waterways, hasPart, Yauza River]
  • A. Yauza River chosen
    The Yauza River is a small river in Moscow, Russia, that flows through the city’s northeastern districts before joining the Moskva River.
  • B. Oshmyanka River
    The Oshmyanka River is a waterway in eastern Europe that flows through the town of Oszmiana (Ashmyany) in present-day Belarus.
  • C. Yaga River
    The Yaga River is a mountain river in the Spanish Pyrenees that carves through the Escuaín Gorge within the Ordesa y Monte Perdido National Park.
  • D. Fontanka River
    The Fontanka River is a major distributary of the Neva in Saint Petersburg, Russia, known for its historic embankments, bridges, and role in defining the city’s central layout.
  • E. Izhora River
    The Izhora River is a small river in northwestern Russia that flows through the Leningrad Oblast and Saint Petersburg region before joining the Neva 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_69d87f22c7248190a54c949738441e2e completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e249175e24819082e571039e278056 completed April 17, 2026, 2:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01673979608190905afae3071413c0 completed May 11, 2026, 5:20 a.m.
Created at: April 10, 2026, 5:05 a.m.