Triple
T1333967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernhard von Galen |
E28704
|
entity |
| Predicate | usedWarfareMethod |
P709
|
FINISHED |
| Object | artillery bombardment |
—
|
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: artillery bombardment | Statement: [Bernhard von Galen, usedWarfareMethod, artillery bombardment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWarfareMethod Context triple: [Bernhard von Galen, usedWarfareMethod, artillery bombardment]
-
A.
usedWarfareType
chosen
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
B.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
C.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
D.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
E.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e98900819092c54c0fb58b958a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.