Triple

T24581139
Position Surface form Disambiguated ID Type / Status
Subject IFAB annual general meeting E608252 entity
Predicate isKeyEventFor P811 FINISHED
Object global football governance 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: global football governance | Statement: [IFAB annual general meeting, isKeyEventFor, global football governance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyEventFor
Context triple: [IFAB annual general meeting, isKeyEventFor, global football governance]
  • A. hasKeyEvent chosen
    Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
  • B. isKeyboardWork
    Indicates that an activity or task primarily involves using a keyboard as the main mode of work or input.
  • C. isKeyCharacterIn
    Indicates that an entity plays a central or primary role as a main or significant character within another entity, such as a story, game, or narrative work.
  • D. keyHitter
    Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
  • E. keyState
    Indicates the current status or condition of a key (such as pressed, released, locked, or unlocked) in relation to an associated object or system.
  • 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_69e2c4ce89248190ad99e18f0638dfbb completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a982db00819081038adce05c0b52 completed April 30, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f2a6c1f07081908edf0b521767e79b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:29 a.m.