Triple

T6648869
Position Surface form Disambiguated ID Type / Status
Subject Goal kick E150768 entity
Predicate offsideConsequence P812 FINISHED
Object Attacking team cannot be offside directly from a goal kick 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: Attacking team cannot be offside directly from a goal kick | Statement: [Goal kick, offsideConsequence, Attacking team cannot be offside directly from a goal kick]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offsideConsequence
Context triple: [Goal kick, offsideConsequence, Attacking team cannot be offside directly from a goal kick]
  • A. consequenceForOpponents
    Indicates that one party’s actions or status result in negative outcomes, penalties, or repercussions specifically for their opponents.
  • B. hasConsequence chosen
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • C. announcedConsequence
    Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
  • D. possibleSideEffect
    Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
  • E. aftermathOf
    Indicates that one event, state, or condition occurs as a consequence or result following another event.
  • 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_69c687f1a3048190828b7342f7125d5c completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6ad04d66c8190926ffcbff372643b completed March 27, 2026, 4:15 p.m.
Created at: March 27, 2026, 2:01 p.m.