Triple
T32143257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PMC Wagner |
E820960
|
entity |
| Predicate | advancedTowards |
P17775
|
FINISHED |
| Object | Moscow during June 2023 mutiny |
—
|
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: Moscow during June 2023 mutiny | Statement: [PMC Wagner, advancedTowards, Moscow during June 2023 mutiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancedTowards Context triple: [PMC Wagner, advancedTowards, Moscow during June 2023 mutiny]
-
A.
advancedThrough
chosen
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
B.
treatsAsAdvanced
Indicates that one entity regards or handles another entity as if it were advanced in level, status, or complexity.
-
C.
traditionalLevel
Indicates the degree to which something adheres to established customs, practices, or traditions.
-
D.
hasMoreAdvanced
Indicates that one entity possesses a higher level of advancement, development, or sophistication compared to another entity.
-
E.
typeOfAdvance
Indicates that one entity represents a specific kind or category of advance (e.g., payment, progress, or development) in relation to another entity.
- 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_69f6b9af93e081908d003dd45258ad27 |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.