Triple

T29156607
Position Surface form Disambiguated ID Type / Status
Subject Makanrushi E739061 entity
Predicate hasOfficialLanguageOfAdminState P96074 FINISHED
Object Russian LITERAL 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: Russian | Statement: [Makanrushi, hasOfficialLanguageOfAdminState, Russian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOfficialLanguageOfAdminState
Context triple: [Makanrushi, hasOfficialLanguageOfAdminState, Russian]
  • A. hasOfficialLanguageOfLocation chosen
    Indicates that a location has a specified language recognized as its official language.
  • B. officialLanguageOfSendingState
    Indicates that a particular language is the designated official language used by the state that is sending a representative, document, or communication.
  • C. hasOfficialCountryLanguage
    Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
  • D. usesOfficialLanguageOf
    Indicates that one entity adopts and employs the official language of another entity for communication or formal purposes.
  • E. hasOfficialLanguageOfSurroundingCountry
    Indicates that an entity uses as its official language the same language that is official in the country surrounding it.
  • F. None of above.

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_69f07cb528fc8190a556b73990c347c8 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 28, 2026, 11:45 a.m.