Triple
T854337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Wagram |
E18455
|
entity |
| Predicate | artilleryUsage |
P709
|
FINISHED |
| Object | featured massive artillery bombardments |
—
|
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: featured massive artillery bombardments | Statement: [Battle of Wagram, artilleryUsage, featured massive artillery bombardments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artilleryUsage Context triple: [Battle of Wagram, artilleryUsage, featured massive artillery bombardments]
-
A.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
usedWarfareType
chosen
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
D.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
E.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3a48c08190b4677d825fcbfaf9 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.