Triple

T2171459
Position Surface form Disambiguated ID Type / Status
Subject USS Forrestal (CV-59) E48434 entity
Predicate notableEventDescription P2107 FINISHED
Object catastrophic flight deck fire and explosions during Vietnam War operations 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: catastrophic flight deck fire and explosions during Vietnam War operations | Statement: [USS Forrestal (CV-59), notableEventDescription, catastrophic flight deck fire and explosions during Vietnam War operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableEventDescription
Context triple: [USS Forrestal (CV-59), notableEventDescription, catastrophic flight deck fire and explosions during Vietnam War operations]
  • A. notableEventResponse
    Indicates a response, reaction, or consequence that occurs as a result of a notable event.
  • B. notableEventDate
    Indicates the date on which a notable or significant event associated with the subject occurred.
  • C. famousForEvent
    Indicates that an entity is widely known or recognized specifically because of a particular event.
  • D. notableEventCoverage
    Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
  • E. hasHistoricalEvent chosen
    Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
  • 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_69a88aa3faa48190995b233af6525815 completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc1559ff481908efe3f214b2570dc completed March 7, 2026, 6:10 a.m.
PD Predicate disambiguation batch_69abbd9efc1c81909a65044a1ffc9038 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:45 p.m.