Triple
T28309712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pattern 1853 socket bayonet |
E713961
|
entity |
| Predicate | combatTechnique |
P35675
|
FINISHED |
| Object | bayonet charge |
—
|
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: bayonet charge | Statement: [Pattern 1853 socket bayonet, combatTechnique, bayonet charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatTechnique Context triple: [Pattern 1853 socket bayonet, combatTechnique, bayonet charge]
-
A.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
B.
offensiveSkill
Indicates a relationship where an entity possesses or demonstrates the ability to perform actions aimed at attacking, scoring, or otherwise advancing an offensive objective.
-
C.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
E.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:39 p.m.