Triple

T33074343
Position Surface form Disambiguated ID Type / Status
Subject Operation Iron Swords E846316 entity
Predicate legalJustificationClaimedByIsrael P198970 FINISHED
Object right of self-defense 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: right of self-defense | Statement: [Operation Iron Swords, legalJustificationClaimedByIsrael, right of self-defense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalJustificationClaimedByIsrael
Context triple: [Operation Iron Swords, legalJustificationClaimedByIsrael, right of self-defense]
  • A. strategicRationaleForIsrael
    Indicates that something serves as a strategic justification, motive, or benefit specifically in favor of Israel.
  • B. landStatusClaimedByIsrael
    Indicates that the land in question is claimed by Israel as part of its sovereign territory or jurisdiction.
  • C. regardsStateOfIsraelAs
    Indicates how an entity views, judges, or holds an attitude toward the State of Israel.
  • D. militaryObjectiveOfIsrael
    Indicates that something is a target or goal designated as a military objective by Israel.
  • E. legalRationaleClaimedByTurkey
    Indicates that a particular legal rationale is asserted or invoked by Turkey as the basis for its position or actions.
  • F. None of above. chosen

Provenance (4 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_69f3495405b88190967af2157b43b896 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff17be6ad48190963206f2619b1b28 completed May 9, 2026, 11:17 a.m.
PD Predicate disambiguation batch_69ff1724ba24819092c928fcbcb286ec completed May 9, 2026, 11:14 a.m.
PDg Predicate description generation batch_69ff17bda59c8190b27c524f3e01c6df completed May 9, 2026, 11:17 a.m.
Created at: May 1, 2026, 1:25 a.m.