Triple
T6798918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Second Army |
E156130
|
entity |
| Predicate | resultAtTannenberg |
P19109
|
FINISHED |
| Object | encircled and largely destroyed |
—
|
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: encircled and largely destroyed | Statement: [Russian Second Army, resultAtTannenberg, encircled and largely destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAtTannenberg Context triple: [Russian Second Army, resultAtTannenberg, encircled and largely destroyed]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
resultInArdennes
Indicates that one event, action, or condition leads to or causes an outcome specifically occurring in the Ardennes region.
-
C.
enemyEngagementAtJutland
Indicates that an entity participated in or was involved in hostile military action against an enemy during the Battle of Jutland.
-
D.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
E.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2cb6b2881909b30bb8020a9d3bf |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.