Triple
T32143225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PMC Wagner |
E820960
|
entity |
| Predicate | roleInUkraine |
P108011
|
FINISHED |
| Object | frontline assault operations |
—
|
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: frontline assault operations | Statement: [PMC Wagner, roleInUkraine, frontline assault operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUkraine Context triple: [PMC Wagner, roleInUkraine, frontline assault operations]
-
A.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
B.
roleInRussia
Indicates that an entity holds or has held an official or notable role, position, or function within the context of Russia.
-
C.
roleInSovietUnion
Indicates that an entity held a specific position, function, or status within the governmental, political, or institutional structure of the Soviet Union.
-
D.
roleInPoland
Indicates that an entity holds or has held a specific role, position, or function within the context of Poland.
-
E.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 1, 2026, 12:31 a.m.