Triple
T28235920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFIRI Competitions Committee |
E711879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | football competitions committee |
C21269
|
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: football competitions committee Context triple: [FFIRI Competitions Committee, instanceOf, football competitions committee]
-
A.
football competition organizer
chosen
A football competition organizer is an entity responsible for planning, coordinating, and managing all aspects of a football tournament or league, including scheduling, regulations, logistics, and stakeholder communication.
-
B.
football competition sanctioning framework
A football competition sanctioning framework is a structured set of rules, criteria, and procedures used by governing bodies to approve, regulate, and oversee official football tournaments and leagues.
-
C.
football competitions
Organized sporting events in which football teams compete against each other under defined rules and structures, such as leagues, tournaments, and cups, to determine rankings or champions.
-
D.
club football competition
A club football competition is an organized tournament or league in which football clubs compete against each other under a defined set of rules and structure to determine rankings, titles, or championships.
-
E.
football law-making body
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.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:55 p.m.