Triple
T1452473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Group Don |
E31321
|
entity |
| Predicate | failedToAchieve |
P12733
|
FINISHED |
| Object | Breakout or relief of 6th Army |
—
|
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: Breakout or relief of 6th Army | Statement: [Army Group Don, failedToAchieve, Breakout or relief of 6th Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failedToAchieve Context triple: [Army Group Don, failedToAchieve, Breakout or relief of 6th Army]
-
A.
missionFailure
chosen
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
B.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
C.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
-
D.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
E.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57d34cc8190801b769d9d9b2e2e |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.