Triple
T7626000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Uranus |
E172632
|
entity |
| Predicate | exploitedWeakness |
P33834
|
FINISHED |
| Object | Axis allied armies on the flanks |
—
|
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: Axis allied armies on the flanks | Statement: [Operation Uranus, exploitedWeakness, Axis allied armies on the flanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitedWeakness Context triple: [Operation Uranus, exploitedWeakness, Axis allied armies on the flanks]
-
A.
exploits
chosen
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
B.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
C.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
-
D.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
E.
weakenedDuring
Indicates that an entity’s strength, intensity, or effectiveness is reduced over the course of a specified time period or event.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.