Triple
T17274207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Komsomolskoye |
E419342
|
entity |
| Predicate | encirclement |
P10171
|
FINISHED |
| Object | Chechen fighters |
—
|
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: Chechen fighters | Statement: [Battle of Komsomolskoye, encirclement, Chechen fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encirclement Context triple: [Battle of Komsomolskoye, encirclement, Chechen fighters]
-
A.
directionOfEncirclement
Indicates the directional orientation (e.g., clockwise or counterclockwise) in which one entity surrounds or encircles another.
-
B.
encircledForce
Indicates that a military force is surrounded by enemy units, cutting off its movement or escape routes.
-
C.
encirclementOperation
chosen
Indicates a military action in which forces maneuver to surround an opposing force, cutting off its escape routes and lines of support.
-
D.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
E.
surroundedCity
Indicates that one city is encircled or completely enclosed by another city or its surrounding territory.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4c209c81909c713ed78f2cb19a |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.