Triple
T24818262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Герой Российской Федерации |
E620984
|
entity |
| Predicate | официальноеНазвание |
P66
|
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.
officialName
chosen
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
-
B.
firstOfficialName
Indicates the original or primary official name formally assigned to an entity before any subsequent name changes or alternatives.
-
C.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
D.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
E.
officialNameGivenBy
Indicates that an official or formal name has been assigned to an entity by a specific authority or source.
- 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.