Triple
T16974525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tarutino |
E411774
|
entity |
| Predicate | RussianTactics |
P31112
|
FINISHED |
| Object | night march and dawn assault |
—
|
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: night march and dawn assault | Statement: [Battle of Tarutino, RussianTactics, night march and dawn assault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RussianTactics Context triple: [Battle of Tarutino, RussianTactics, night march and dawn assault]
-
A.
RussianObjective
Indicates that an entity has an objective, goal, or target specifically related to Russia (e.g., Russian interests, territory, institutions, or actors).
-
B.
strategyUsedByRussians
chosen
Indicates a strategy or tactic that is employed or implemented by Russians.
-
C.
RussiaControls
Indicates that Russia exercises authority, influence, or governing power over the specified entity or territory.
-
D.
PersianTactics
Indicates the use or application of military strategies, maneuvers, or methods characteristic of Persian forces in a conflict or battle context.
-
E.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18300c8819080c8bf19962754ba |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.