Triple
T2030573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vimy Ridge |
E44505
|
entity |
| Predicate | artillerySupport |
P34729
|
FINISHED |
| Object | over 900 guns and mortars |
—
|
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: over 900 guns and mortars | Statement: [Battle of Vimy Ridge, artillerySupport, over 900 guns and mortars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artillerySupport Context triple: [Battle of Vimy Ridge, artillerySupport, over 900 guns and mortars]
-
A.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
B.
artilleryUsedFor
Indicates that artillery is employed or utilized for a particular purpose, function, or objective.
-
C.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
D.
navalSupportFrom
Indicates the provision of naval assistance or backing from one entity to another, such as military, logistical, or operational support delivered via sea forces.
-
E.
suppliedTroopsTo
Indicates that one entity provided military personnel or forces to another entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.