Triple
T24818284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Герой Российской Федерации |
E620984
|
entity |
| Predicate | органПрисвоения |
P121567
|
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.
имеетОрган
Indicates that one entity possesses or contains a specific organ as a part of its body.
-
B.
органЭмиссии
chosen
Indicates the authority or body responsible for issuing or emitting something (such as a document, instrument, or asset).
-
C.
organType
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
-
D.
organ
Indicates that one entity is an organ (a functional body part) of another entity.
-
E.
tipoDeÓrgano
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
- 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.