Triple

T18620678
Position Surface form Disambiguated ID Type / Status
Subject Droppin Well bar E455138 entity
Predicate hasCasualtiesInAttack P52637 FINISHED
Object 11 British soldiers killed 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: 11 British soldiers killed | Statement: [Droppin Well bar, hasCasualtiesInAttack, 11 British soldiers killed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCasualtiesInAttack
Context triple: [Droppin Well bar, hasCasualtiesInAttack, 11 British soldiers killed]
  • A. hasCasualtiesLevel
    Indicates the severity or extent of casualties associated with an event, incident, or situation.
  • B. sustainedHeavyCasualtiesAt
    Indicates that an entity experienced a large number of serious losses (e.g., deaths or injuries) at a specific location or during a specific event.
  • C. casualtiesInflictedOn chosen
    Indicates that one party has caused deaths or injuries to another party as a result of a harmful event or action.
  • D. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • E. casualtiesIncluded
    Indicates that the referenced count or report of casualties explicitly includes the specified individuals or groups.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f00889c8190931f8d3fbabd531b completed April 19, 2026, 9:54 p.m.
PD Predicate disambiguation batch_69e478d4a7948190a4bb9223bb5dddfc completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:46 a.m.