Triple

T377032
Position Surface form Disambiguated ID Type / Status
Subject 1984 Summer Olympics E8393 entity
Predicate boycottReason P7622 FINISHED
Object retaliation for U.S.-led boycott of 1980 Moscow Olympics 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: retaliation for U.S.-led boycott of 1980 Moscow Olympics | Statement: [1984 Summer Olympics, boycottReason, retaliation for U.S.-led boycott of 1980 Moscow Olympics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boycottReason
Context triple: [1984 Summer Olympics, boycottReason, retaliation for U.S.-led boycott of 1980 Moscow Olympics]
  • A. cancellationReason chosen
    Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
  • B. reasonForDecline
    Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
  • C. selectionReason
    Indicates the reason or justification for choosing or selecting one entity over alternatives.
  • D. opposedBy
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
  • E. reasonWritten
    Indicates that one entity is the reason or motivation for which another entity was written or authored.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec1804108190a1e94526b71289ea completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e96351cc8190a55adf95f8c27e9e completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.