Triple
T24818288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Герой Российской Федерации |
E620984
|
entity |
| Predicate | языкОфициальногоНазвания |
P26955
|
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.
hasLanguageOfOfficialName
chosen
Indicates that an entity’s official name is expressed in a specified language.
-
B.
formerOfficialNameLanguage
Indicates the language in which an entity’s former official name was expressed.
-
C.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
D.
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.
-
E.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:03 a.m.