Triple

T21656910
Position Surface form Disambiguated ID Type / Status
Subject Совет глав правительств ШОС E534490 entity
Predicate языкРаботы P118239 FINISHED
Object русский язык 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: русский язык | Statement: [Совет глав правительств ШОС, языкРаботы, русский язык]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: русский язык
Context triple: [Совет глав правительств ШОС, языкРаботы, русский язык]
  • A. Rus
    Rus is a prominent Russian MVD special forces unit known for high-risk counter-terrorism and hostage-rescue operations.
  • B. Rus
    Rus was a medieval East Slavic cultural and political realm that laid the foundations for the modern nations of Russia, Ukraine, and Belarus.
  • C. Russan
    Russan is a commune in southern France situated along the Gardon River.
  • D. 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.
  • E. 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.
  • 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5919c9c88190a2ddcf2cefee79a5 completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:36 p.m.