Triple
T2271073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kiev (1941) |
E50657
|
entity |
| Predicate | SovietObjective |
P37592
|
FINISHED |
| Object | defend Kiev |
—
|
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: defend Kiev | Statement: [Battle of Kiev (1941), SovietObjective, defend Kiev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SovietObjective Context triple: [Battle of Kiev (1941), SovietObjective, defend Kiev]
-
A.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
-
B.
SovietOperation
Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
-
C.
RussianObjective
Indicates that an entity has an objective, goal, or target specifically related to Russia (e.g., Russian interests, territory, institutions, or actors).
-
D.
RussoAustrianObjective
Indicates a shared objective or goal jointly pursued by Russian and Austrian parties or forces.
-
E.
commanderForSovietSide
Indicates that an entity serves as a military commander representing or leading forces on the Soviet side in a conflict or operation.
- F. None of above. chosen
Provenance (4 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc39b2f548190a38f604e0d36db3a |
completed | March 7, 2026, 6:20 a.m. |
Created at: March 4, 2026, 7:48 p.m.