Triple
T24566183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Football Negotiating and Consultative Committee |
E607794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | football governance committee |
C5768
|
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 governance committee Context triple: [Professional Football Negotiating and Consultative Committee, instanceOf, football governance committee]
-
A.
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.
-
B.
sports governing committee
chosen
A sports governing committee is an organized body responsible for setting rules, overseeing competitions, and making policy decisions to regulate and promote a particular sport or group of sports.
-
C.
football association
A football association is an organized governing body responsible for overseeing, regulating, and promoting the sport of football within a specific region or jurisdiction.
-
D.
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.
-
E.
BBC governing body
The BBC governing body is the overarching authority responsible for setting the strategic direction, ensuring editorial independence, and overseeing the accountability and performance of the British Broadcasting Corporation.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:28 a.m.