Triple
T13906379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligue de Football Professionnel |
E334362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | football league system operator |
C11247
|
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 league system operator Context triple: [Ligue de Football Professionnel, instanceOf, football league system operator]
-
A.
soccer league operator
chosen
A soccer league operator is an entity responsible for organizing, managing, and regulating soccer competitions, including scheduling matches, enforcing rules, coordinating teams and officials, and overseeing league logistics and governance.
-
B.
association football league system
An association football league system is a hierarchical structure of interconnected football leagues, typically organized by promotion and relegation, that determines the competitive levels and progression of clubs within a country or region.
-
C.
soccer league
A soccer league is an organized competition in which multiple soccer teams play a scheduled series of matches over a season to determine rankings and often a champion.
-
D.
football competition organizer
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.
-
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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.