Triple

T11802505
Position Surface form Disambiguated ID Type / Status
Subject upper Don River E280660 entity
Predicate flowsNear P350 FINISHED
Object city of Oryol E823393 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: city of Oryol | Statement: [upper Don River, flowsNear, city of Oryol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Oryol
Context triple: [upper Don River, flowsNear, city of Oryol]
  • A. city of Oryol chosen
    The city of Oryol is a historic regional center in western Russia, known for its literary heritage and role as the administrative capital of Oryol Oblast.
  • B. Pereiaslavl
    Pereiaslavl was one of the principal urban centers of Kyivan Rus, serving as an important political, military, and cultural hub in medieval Eastern Europe.
  • C. city of Uglich
    The city of Uglich is a historic town in Russia known for its medieval architecture and its role in the events surrounding the death of Tsarevich Dmitry, a key episode in Russian history.
  • D. Oryol
    Oryol was a notable warship of the Imperial Russian Navy, recognized for its role in Russia’s early modern naval history.
  • E. Ivangorod
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a5a2048190b68027f622366079 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f1314300248190847b9c61bbfda121 completed April 28, 2026, 10:14 p.m.
Created at: April 8, 2026, 9:42 p.m.