Triple
T24818283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Герой Российской Федерации |
E620984
|
entity |
| Predicate | можетБытьПрисвоено |
P13666
|
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.
mayBeAssignedBy
Indicates that an entity has the potential or permission to be assigned by another entity, without asserting that the assignment has actually occurred.
-
B.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
-
C.
canBeReassignedBy
Indicates that one entity has the authority or ability to change or transfer another entity’s assignment or allocation.
-
D.
isTypicallyAssignedAt
Indicates that something is most commonly or customarily designated, allocated, or given at a particular time, place, or context.
-
E.
canBeDesignatedBy
chosen
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:03 a.m.