Triple

T15923734
Position Surface form Disambiguated ID Type / Status
Subject Mille Miglia E386153 entity
Predicate cancellationCause P7622 FINISHED
Object fatal crash involving spectators in 1957 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: fatal crash involving spectators in 1957 | Statement: [Mille Miglia, cancellationCause, fatal crash involving spectators in 1957]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cancellationCause
Context triple: [Mille Miglia, cancellationCause, fatal crash involving spectators in 1957]
  • A. cancellationReason chosen
    Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
  • B. canceledBy
    Indicates that an action, event, or agreement was annulled or called off by a specific entity.
  • C. cancellation
    Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
  • D. reasonForAnnulment
    Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
  • E. cancellationAnnouncedOn
    Indicates that the cancellation of something (e.g., an event, service, or agreement) was publicly announced on a specific date or time.
  • 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_69d86da750008190987eb26be3f6c118 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e172b48b308190bc430b2308cbc75b completed April 16, 2026, 11:37 p.m.
PD Predicate disambiguation batch_69e142cf5c548190a931f7b58144cd31 completed April 16, 2026, 8:13 p.m.
Created at: April 10, 2026, 4:52 a.m.