Triple
T3489032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Perekop (1941) |
E73679
|
entity |
| Predicate | combatantsClassification |
P21502
|
FINISHED |
| Object | Axis vs Soviet forces |
—
|
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: Axis vs Soviet forces | Statement: [Battle of Perekop (1941), combatantsClassification, Axis vs Soviet forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsClassification Context triple: [Battle of Perekop (1941), combatantsClassification, Axis vs Soviet forces]
-
A.
combatantsIncluded
chosen
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
combatantLanguage
Indicates the language used by a combatant in a conflict or competitive interaction.
-
E.
mainCombatant
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb92b3ac8190b8675f5a5e9d4408 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.