Triple
T38580952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Buryatia |
E932240
|
entity |
| Predicate | officialLanguageOfEntity |
P112296
|
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: [Coat of arms of Buryatia, officialLanguageOfEntity, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialLanguageOfEntity Context triple: [Coat of arms of Buryatia, officialLanguageOfEntity, Russian]
-
A.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
B.
declaresOfficialLanguageOf
Indicates that an authority formally designates a particular language as the official language of a specified entity or jurisdiction.
-
C.
hasLanguageOfficial
chosen
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
D.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
E.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:32 p.m.