Triple

T19385825
Position Surface form Disambiguated ID Type / Status
Subject administration of Chaunsky District E484930 entity
Predicate hasOfficialLanguage P236 FINISHED
Object Russian language 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: Russian language | Statement: [administration of Chaunsky District, hasOfficialLanguage, Russian language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Russian language
Context triple: [administration of Chaunsky District, hasOfficialLanguage, Russian language]
  • A. Russian language chosen
    Russian is an East Slavic language spoken primarily in Russia and neighboring countries, serving as one of the world's major languages in politics, science, and culture.
  • B. Russian
    Russian is an East Slavic language that serves as the official language of Russia and a major lingua franca across much of Eastern Europe and Central Asia.
  • C. Russan
    Russan is a commune in southern France situated along the Gardon River.
  • D. Russo
    Russo is an Italian surname commonly used as a variant of Rossi, often associated with people of Italian heritage.
  • E. Rus
    Rus was a medieval East Slavic cultural and political realm that laid the foundations for the modern nations of Russia, Ukraine, and Belarus.
  • 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61b40d1148190b4fcd9ad56aa6910 completed April 20, 2026, 12:25 p.m.
Created at: April 10, 2026, 1:35 p.m.