Triple
T30654587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Camerone |
E780349
|
entity |
| Predicate | tacticalContext |
P70101
|
FINISHED |
| Object | protection of a supply convoy |
—
|
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: protection of a supply convoy | Statement: [Battle of Camerone, tacticalContext, protection of a supply convoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalContext Context triple: [Battle of Camerone, tacticalContext, protection of a supply convoy]
-
A.
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.
-
B.
tacticalIssue
Indicates a relationship where an entity is involved in, affected by, or characterized as a specific tactical problem, challenge, or concern within an operational context.
-
C.
hasTacticalSituation
chosen
Indicates that an entity is associated with, or is operating within, a specific tactical situation or context.
-
D.
tacticalComplexity
Indicates the degree to which an action, plan, or interaction involves intricate, multi-layered tactical considerations or maneuvers.
-
E.
tacticalSystem
Indicates a relationship where an entity functions as or is associated with a tactical system used for planning, coordinating, or executing tactical operations.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9b821c8190bf6d788b02a58baa |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.