Triple

T27796475
Position Surface form Disambiguated ID Type / Status
Subject Burnden Park E702124 entity
Predicate Burnden Park disaster P163361 FINISHED
Object occurred 9 March 1946 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: occurred 9 March 1946 | Statement: [Burnden Park, Burnden Park disaster, occurred 9 March 1946]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: Burnden Park disaster
Context triple: [Burnden Park, Burnden Park disaster, occurred 9 March 1946]
  • A. 2004 cockling disaster
    Indicates a disastrous event involving cockle harvesting that occurred in 2004, typically implying severe harm or loss of life among those involved.
  • B. firstMajorAccidentDescription
    Indicates the textual description of an entity’s first major accident.
  • C. accidentOccurredDuring
    Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
  • D. otherMajorTragedy
    Indicates that the subject experienced or was involved in a significant tragic event other than the primary or most notable tragedy under consideration.
  • E. miningDisaster
    Indicates a disastrous event occurring in the context of mining operations, typically involving significant damage, injury, or loss of life.
  • 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_69ef8408e0588190977cffa32dc33a29 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6380bac808190ab257444c38d24d2 completed May 2, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69f6318ae6f08190b3f85f9201046a15 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6359d46b88190922dd7de508e3b0e completed May 2, 2026, 5:34 p.m.
Created at: April 27, 2026, 5:31 p.m.