Triple

T17455520
Position Surface form Disambiguated ID Type / Status
Subject Swiss mercenaries E425016 entity
Predicate tacticalWeakness P47330 FINISHED
Object vulnerability to artillery 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: vulnerability to artillery | Statement: [Swiss mercenaries, tacticalWeakness, vulnerability to artillery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tacticalWeakness
Context triple: [Swiss mercenaries, tacticalWeakness, vulnerability to artillery]
  • A. hasWeakness chosen
    Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
  • 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. tacticalFeatureUsed
    Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
  • D. tacticalStyle
    Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
  • E. 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.
  • 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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e45141e1d48190b7de9159f1fd71fa completed April 19, 2026, 3:51 a.m.
PD Predicate disambiguation batch_69e3b4f0e3fc819094e466b74622c956 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.