Triple
T10120596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of Labour of the Russian Federation |
E223275
|
entity |
| Predicate | rewardIncludes |
P13061
|
FINISHED |
| Object | state certificate |
—
|
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: state certificate | Statement: [Hero of Labour of the Russian Federation, rewardIncludes, state certificate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardIncludes Context triple: [Hero of Labour of the Russian Federation, rewardIncludes, state certificate]
-
A.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
B.
offersRewardFor
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
C.
awardIncludes
chosen
Indicates that a particular award encompasses, contains, or is composed of the specified component, category, or sub-award.
-
D.
rewardBrand
Indicates that one entity grants or associates a reward with a particular brand.
-
E.
grantedAsRewardFor
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd266b18c8190b35fe637c912e756 |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.