Triple

T27796477
Position Surface form Disambiguated ID Type / Status
Subject Burnden Park E702124 entity
Predicate Burnden Park disaster P163361 FINISHED
Object over 400 spectators injured 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: over 400 spectators injured | Statement: [Burnden Park, Burnden Park disaster, over 400 spectators injured]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: Burnden Park disaster
Context triple: [Burnden Park, Burnden Park disaster, over 400 spectators injured]
  • A. Burnden Park disaster chosen
    Indicates a tragic incident or disaster that occurred at Burnden Park, typically involving significant harm or loss of life among people present there.
  • B. 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.
  • C. firstMajorAccidentDescription
    Indicates the textual description of an entity’s first major accident.
  • D. accidentOccurredDuring
    Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
  • E. otherMajorTragedy
    Indicates that the subject experienced or was involved in a significant tragic event other than the primary or most notable tragedy under consideration.
  • 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_69ef8408e0588190977cffa32dc33a29 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6895f0819088655277e45859a8 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 5:31 p.m.