Triple
T10472917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagon Box Fight |
E246971
|
entity |
| Predicate | tacticsNativeForces |
P48051
|
FINISHED |
| Object | mounted charges |
—
|
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: mounted charges | Statement: [Wagon Box Fight, tacticsNativeForces, mounted charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsNativeForces Context triple: [Wagon Box Fight, tacticsNativeForces, mounted charges]
-
A.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
B.
militaryTacticsFaced
chosen
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
C.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
E.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094daac081908e0ba5e10c1bbb67 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.