Triple
T31618591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | СССР |
E806831
|
entity |
| Predicate | официальныйЯзык |
P236
|
FINISHED |
| Object | русский язык |
—
|
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: русский язык | Statement: [СССР, официальныйЯзык, русский язык]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: официальныйЯзык Context triple: [СССР, официальныйЯзык, русский язык]
-
A.
officialLanguage
chosen
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.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
C.
previousOfficialLanguage
Indicates that one language formerly held official status in a country, region, or organization before being replaced or losing that status.
-
D.
laterOfficialLanguage
Indicates that one language became an official language of an entity at a later time than another language.
-
E.
usesOfficialLanguageOf
Indicates that one entity adopts and employs the official language of another entity for communication or formal purposes.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8acae308190b3450346a6bb55bc |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:40 p.m.