Triple

T36075198
Position Surface form Disambiguated ID Type / Status
Subject 1984 Brazilian Grand Prix E1043477 entity
Predicate ayrtonSennaRetirementCause P185031 FINISHED
Object turbo failure 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: turbo failure | Statement: [1984 Brazilian Grand Prix, ayrtonSennaRetirementCause, turbo failure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ayrtonSennaRetirementCause
Context triple: [1984 Brazilian Grand Prix, ayrtonSennaRetirementCause, turbo failure]
  • A. ayrtonSennaResult
    Indicates the race result or finishing status associated with Ayrton Senna in a given event or competition.
  • B. motorRacingCeasedBecauseOf
    Indicates that a motor racing activity, event, or series stopped occurring as a result of a specified cause or reason.
  • C. retiredFromRacing
    Indicates that an entity has permanently stopped participating in competitive racing activities.
  • D. activeInFormulaOneUntil
    Indicates that an entity participated as an active competitor in Formula One up to and including a specified end time or season.
  • E. retiredFromPlayingDueTo
    Indicates that an individual stopped actively participating in a sport or game because of the specified reason or cause.
  • 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_69f76e2fd3248190b900d9a492bf5a7a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb1d6b70819091227bd011734d19 completed May 3, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
PDg Predicate description generation batch_69f7ba6c27e081908868a2b50d1d603c completed May 3, 2026, 9:13 p.m.
Created at: May 3, 2026, 4:08 p.m.