Triple

T4339299
Position Surface form Disambiguated ID Type / Status
Subject Docklands bombing E97539 entity
Predicate ceasefireEnded P56134 FINISHED
Object 1994–1996 IRA ceasefire 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: 1994–1996 IRA ceasefire | Statement: [Docklands bombing, ceasefireEnded, 1994–1996 IRA ceasefire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ceasefireEnded
Context triple: [Docklands bombing, ceasefireEnded, 1994–1996 IRA ceasefire]
  • A. ceasefireDeclared
    Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
  • B. ceasefireDate
    Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
  • C. ceasefireResolution
    Indicates a formal decision or agreement to halt hostilities or armed conflict between opposing parties, typically under specified terms and conditions.
  • D. ceasefireBrokeredBy
    Indicates that a ceasefire agreement was arranged or facilitated through the mediation efforts of a specific party or entity.
  • E. announcedCeasefire
    Indicates that an entity has formally declared the suspension of hostilities or fighting, typically within a conflict or war.
  • 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_69b3454662a481908fbcd0bbfaa3a0a4 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3516dffb48190878f81ffe71a5e82 completed March 12, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69b34f4fe1c481908d6d66e15697c04b completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b350d1649881908fa6556d875a8b4d completed March 12, 2026, 11:48 p.m.
Created at: March 12, 2026, 11:14 p.m.