Triple
T24581101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFAB annual general meeting |
E608252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football rules meeting |
C6272
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: association football rules meeting Context triple: [IFAB annual general meeting, instanceOf, association football rules meeting]
-
A.
football law-making body
chosen
A football law-making body is an authoritative organization responsible for creating, interpreting, and updating the official rules and regulations that govern how football is played worldwide.
-
B.
association football referee
An association football referee is the official responsible for enforcing the Laws of the Game on the field, making decisions on play, fouls, and disciplinary actions to ensure a fair and safe match.
-
C.
association football organization
An association football organization is an entity that governs, manages, or coordinates the playing, administration, and development of soccer competitions, clubs, and related activities within a defined scope or jurisdiction.
-
D.
FIFA Congress
The FIFA Congress is the supreme legislative and decision-making body of FIFA, comprising representatives from all member associations who convene to set policies, elect officials, and amend regulations governing international football.
-
E.
association football season topic
An association football season topic represents the organized set of competitions, matches, teams, and related events that occur within a defined time period for a particular league, club, or competition in the sport of soccer.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 18, 2026, 2:29 a.m.