Triple

T19629682
Position Surface form Disambiguated ID Type / Status
Subject Gus-Khrustalny E471232 entity
Predicate locatedOn P40 FINISHED
Object Gus 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: Gus River | Statement: [Gus-Khrustalny, locatedOn, Gus River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gus River
Context triple: [Gus-Khrustalny, locatedOn, Gus River]
  • A. Gus River chosen
    The Gus River is a waterway in Vladimir Oblast, Russia, that lends its name to the town of Gus-Khrustalny and is part of the region’s historical glassmaking area.
  • B. Lez River
    The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
  • C. Ager River
    The Ager River is a watercourse in Upper Austria that flows through the Salzkammergut region and ultimately joins the Traun River.
  • D. Gavaraget River
    The Gavaraget River is a watercourse in Armenia that serves as one of the tributaries feeding into Lake Sevan.
  • E. Vyg River
    The Vyg River is a watercourse in northwestern Russia that flows through Karelia before emptying into the White Sea.
  • 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e64101a0448190ba19f8917ae85dd6 completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:44 p.m.