Triple
T11614092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalingrad area |
E275460
|
entity |
| Predicate | majorBattleStart |
P92660
|
FINISHED |
| Object | August 1942 |
—
|
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: August 1942 | Statement: [Stalingrad area, majorBattleStart, August 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBattleStart Context triple: [Stalingrad area, majorBattleStart, August 1942]
-
A.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
B.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
C.
startOfMajorConflict
chosen
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
-
D.
isFirstMajorBattleOf
Indicates that a battle is the earliest significant or primary large-scale engagement within a particular war, campaign, or conflict.
-
E.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a044a3088190b92f4674c2d0b443 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.