Triple

T4627701
Position Surface form Disambiguated ID Type / Status
Subject Mytishchi E101138 entity
Predicate locatedOn P40 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: [Mytishchi, locatedOn, Yauza River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yauza River
Context triple: [Mytishchi, locatedOn, 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. 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.
  • C. 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.
  • D. Sheksna River
    The Sheksna River is a significant waterway in northwestern Russia that forms part of the Volga–Baltic Waterway, connecting the Volga River basin with the Baltic Sea.
  • E. Snezhnaya River
    The Snezhnaya River is a Siberian river in Russia that serves as one of the tributaries feeding into Lake Baikal.
  • 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_69bd43d0497c8190ac23c65c5804846a completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a2e9780819081add547c760abc9 completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69be819fa79481908b35c424bff0c939 completed March 21, 2026, 11:31 a.m.
Created at: March 20, 2026, 1:13 p.m.