Triple
T4870251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian mobilization (2022) |
E109068
|
entity |
| Predicate | announcedStrength |
P4650
|
FINISHED |
| Object | 300000 reservists |
—
|
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: 300000 reservists | Statement: [Russian mobilization (2022), announcedStrength, 300000 reservists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedStrength Context triple: [Russian mobilization (2022), announcedStrength, 300000 reservists]
-
A.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
B.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
C.
announcedThrough
Indicates that an announcement or communication was made via a particular medium, channel, or intermediary.
-
D.
standardAnnounced
Indicates that an official standard has been formally announced or made public.
-
E.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.