Triple
T18107161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Club Competitions Ranking |
E433374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | AFC competition allocation mechanism |
C21164
|
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: AFC competition allocation mechanism Context triple: [AFC Club Competitions Ranking, instanceOf, AFC competition allocation mechanism]
-
A.
club competition system
A club competition system is a structured framework that manages the organization, scheduling, scoring, and ranking of clubs and their members across various competitive events and seasons.
-
B.
promotion and relegation system
A promotion and relegation system is a hierarchical league structure in which teams move up to higher divisions or down to lower ones based on their competitive performance each season.
-
C.
football competition sanctioning framework
chosen
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.
-
D.
UEFA coefficient
A UEFA coefficient is a numerical ranking system used by the Union of European Football Associations to evaluate and seed clubs and national teams based on their performance in European competitions over a rolling multi-year period.
-
E.
competition grouping
Competition grouping is the conceptual class that organizes participants into structured sets or divisions within a competition based on defined criteria such as skill level, age, region, or qualification results.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:28 a.m.