Triple
T38476915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firing Range |
E915572
|
entity |
| Predicate | hasTacticalFocus |
P75868
|
FINISHED |
| Object | map control |
—
|
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: map control | Statement: [Firing Range, hasTacticalFocus, map control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTacticalFocus Context triple: [Firing Range, hasTacticalFocus, map control]
-
A.
hasPrimaryTactic
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
B.
hasTacticalSituation
Indicates that an entity is associated with, or is operating within, a specific tactical situation or context.
-
C.
hasTacticalMobility
Indicates the capability of an entity to move or be repositioned quickly and effectively within a tactical or operational context.
-
D.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
tacticalPurpose
chosen
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.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.