Triple
T233183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet 62nd Army |
E4451
|
entity |
| Predicate | tactics |
P1716
|
FINISHED |
| Object | close-quarters urban combat |
—
|
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: close-quarters urban combat | Statement: [Soviet 62nd Army, tactics, close-quarters urban combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tactics Context triple: [Soviet 62nd Army, tactics, close-quarters urban combat]
-
A.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
-
C.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
D.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.