Triple

T24471217
Position Surface form Disambiguated ID Type / Status
Subject Camp Holloway E617104 entity
Predicate attackConsequence P100772 FINISHED
Object U.S. casualties and aircraft damage (7 February 1965) 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: U.S. casualties and aircraft damage (7 February 1965) | Statement: [Camp Holloway, attackConsequence, U.S. casualties and aircraft damage (7 February 1965)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: attackConsequence
Context triple: [Camp Holloway, attackConsequence, U.S. casualties and aircraft damage (7 February 1965)]
  • A. attackEffect chosen
    Indicates that one entity’s attack produces a specific effect or consequence on another entity.
  • B. impactOutcome
    Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
  • C. attackOccurred
    Indicates that an act of aggression or violence was carried out by one party against another.
  • D. unexpectedConsequenceOf
    Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
  • E. attacksIf
    Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
  • 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_69e2d7f197588190889a03e620558059 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f299432b2881909502f9cbc7e4dbb0 completed April 29, 2026, 11:50 p.m.
PD Predicate disambiguation batch_69f287d76c7c81909494f12e606a9149 completed April 29, 2026, 10:36 p.m.
Created at: April 18, 2026, 2:20 a.m.