Triple
T8950055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Sabis |
E213321
|
entity |
| Predicate | tacticUsedByNervii |
P1716
|
FINISHED |
| Object | ambush |
—
|
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: ambush | Statement: [Battle of the Sabis, tacticUsedByNervii, ambush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByNervii Context triple: [Battle of the Sabis, tacticUsedByNervii, ambush]
-
A.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
C.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
D.
tacticalPurpose
Indicates the specific tactical objective or intended operational role that an action, asset, or decision is meant to achieve within a broader plan or mission.
-
E.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670b5f50819080f1c73992fe5281 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.