Triple

T19060581
Position Surface form Disambiguated ID Type / Status
Subject Rubtsovsky Bridge E466518 entity
Predicate crosses P416 FINISHED
Object Yauza 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: Yauza River | Statement: [Rubtsovsky Bridge, crosses, Yauza River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yauza River
Context triple: [Rubtsovsky Bridge, crosses, 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. Strelka River
    The Strelka River is a small waterway in the St. Petersburg region of Russia, known primarily for flowing through and giving its name to the settlement of Strelna.
  • D. Khimki River
    The Khimki River is a small waterway in the Moscow region of Russia that serves as a tributary within the local river system and helps feed the nearby Khimki Reservoir.
  • E. Moyka River
    The Moyka River is a small, historic waterway flowing through central Saint Petersburg, lined with notable palaces, embankments, and cultural landmarks.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5dc0910088190b042095937b202a8 completed April 20, 2026, 7:55 a.m.
Created at: April 10, 2026, 12:03 p.m.