Triple
T27087106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on State Awards |
E686062
|
entity |
| Predicate | typeOfAwardReviewed |
P8620
|
FINISHED |
| Object | Orders of the Russian Federation |
—
|
NE NERFINISHED |
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: Orders of the Russian Federation | Statement: [Commission on State Awards, typeOfAwardReviewed, Orders of the Russian Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAwardReviewed Context triple: [Commission on State Awards, typeOfAwardReviewed, Orders of the Russian Federation]
-
A.
awardType
Indicates the specific category or kind of award associated with an entity or event.
-
B.
isAward
Indicates that one entity functions as an award or prize that is given or conferred to another entity.
-
C.
qualificationAwardedBy
Indicates that a particular qualification was granted or conferred by a specific awarding body or institution.
-
D.
isAwardedIn
Indicates that an award or honor is given or conferred within a specific event, context, or time frame.
-
E.
awardTypeOverseen
chosen
Indicates that an entity is responsible for overseeing or managing a particular type or category of award.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 27, 2026, 8:38 a.m.