Triple
T1766443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissar Order |
E38773
|
entity |
| Predicate | mandatedAction |
P29797
|
FINISHED |
| Object | summary execution |
—
|
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: summary execution | Statement: [Commissar Order, mandatedAction, summary execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandatedAction Context triple: [Commissar Order, mandatedAction, summary execution]
-
A.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
B.
mandateFrom
Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
-
C.
canMandate
Indicates that one entity has the authority or power to require another entity to perform or comply with something.
-
D.
mandateDefinedBy
Indicates that the scope, authority, or responsibilities of one entity’s mandate are formally established or specified by another entity or source.
-
E.
mandateForNP
chosen
Indicates that an authority formally requires or authorizes a particular action, policy, or responsibility to be carried out by or for the referenced noun phrase.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.