Triple

T25385010
Position Surface form Disambiguated ID Type / Status
Subject Bloodpack leader Damaskinos’ forces E631497 entity
Predicate tacticalFocus P50132 FINISHED
Object coordinated team assaults 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: coordinated team assaults | Statement: [Bloodpack leader Damaskinos’ forces, tacticalFocus, coordinated team assaults]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tacticalFocus
Context triple: [Bloodpack leader Damaskinos’ forces, tacticalFocus, coordinated team assaults]
  • 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. tacticalStyle chosen
    Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
  • C. 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.
  • D. associatedWithTacticalAcuity
    Indicates a relationship where an entity is linked to, characterized by, or demonstrates tactical acuity in planning or executing actions.
  • 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_69e75a8c50788190aabaa9f96710fc43 completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f5656795248190a732c8596a0e740d completed May 2, 2026, 2:45 a.m.
PD Predicate disambiguation batch_69f4806d93dc8190b9dff4c63186faff completed May 1, 2026, 10:29 a.m.
Created at: April 21, 2026, 1:46 p.m.