Triple

T833029
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Bogside E18008 entity
Predicate opponentTactic P1716 FINISHED
Object CS gas deployment by security forces 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: CS gas deployment by security forces | Statement: [Battle of the Bogside, opponentTactic, CS gas deployment by security forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opponentTactic
Context triple: [Battle of the Bogside, opponentTactic, CS gas deployment by security forces]
  • A. hasCommonTacticOfOpponents
    Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
  • B. tactic chosen
    Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
  • C. opponentObjective
    Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
  • D. opponentAtMidway
    Indicates that one entity is the opposing side or competitor of another in the context of the Midway event, location, or stage.
  • E. defensiveTactics
    Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
  • 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_69a49389f44881909a608fb27d89f247 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4abb647988190950e1790bcfa60a5 completed March 1, 2026, 9:12 p.m.
PD Predicate disambiguation batch_69a4aa7b3d2481909199f7c9f305bdfe completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:38 p.m.