Triple
T22630611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | badges of honor of the Russian Federation |
E558537
|
entity |
| Predicate | requiresDecree |
P92479
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [badges of honor of the Russian Federation, requiresDecree, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDecree Context triple: [badges of honor of the Russian Federation, requiresDecree, yes]
-
A.
containsDecree
Indicates that one entity includes or incorporates a formal decree issued by an authority.
-
B.
requiresDecision
Indicates that a choice or judgment must be made regarding the associated entities or situation.
-
C.
requiredRatificationOf
Indicates that one entity’s decision, agreement, or action must be formally approved or confirmed by another specified entity in order to take effect.
-
D.
requiresOrdinance
chosen
Indicates that one entity can only be established, changed, or carried out if a formal ordinance is enacted or in place.
-
E.
requiresForPlenary
Indicates that one entity must be present, completed, or satisfied as a prerequisite for another entity to proceed to or attain plenary (full or formal) status.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17008e7648190b243c18067b4efb9 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.