Triple
T24818273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Герой Российской Федерации |
E620984
|
entity |
| Predicate | имеетЗнакОтличия |
P133746
|
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.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
B.
hasDistinctiveEmblem
chosen
Indicates that an entity possesses a unique symbol, logo, or emblem that serves to distinguish it from others.
-
C.
distinguishingTrait
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
D.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
E.
hasDistinctFeature
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
- 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.