Triple

T33584466
Position Surface form Disambiguated ID Type / Status
Subject Mark 39 nuclear bomb E860241 entity
Predicate publicRevelationOfAccidentDetails P199002 FINISHED
Object declassified documents in 2013 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: declassified documents in 2013 | Statement: [Mark 39 nuclear bomb, publicRevelationOfAccidentDetails, declassified documents in 2013]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicRevelationOfAccidentDetails
Context triple: [Mark 39 nuclear bomb, publicRevelationOfAccidentDetails, declassified documents in 2013]
  • A. resultOfAccident
    Indicates that something exists or occurs as a consequence or outcome of an accident.
  • B. involvedInAccident
    Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
  • C. accident
    Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
  • D. depictedCauseOfAccident
    Indicates that one entity is shown or represented as the cause of an accident involving another entity.
  • E. causedAccident
    Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
  • 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_69f3497e70e48190951c94d072879bec completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff1a972bf08190860696ffcd887c0f completed May 9, 2026, 11:29 a.m.
PD Predicate disambiguation batch_69ff184005d88190bf38283ebc499b28 completed May 9, 2026, 11:19 a.m.
PDg Predicate description generation batch_69ff1a95b6fc81909331bb03e263b5b9 completed May 9, 2026, 11:29 a.m.
Created at: May 1, 2026, 1:40 a.m.