Triple
T30443329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA regulations |
E774512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UEFA legal instrument |
C57000
|
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: UEFA legal instrument Context triple: [UEFA regulations, instanceOf, UEFA legal instrument]
-
A.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
B.
FIFA regulatory document
A FIFA regulatory document is an official set of rules, guidelines, and procedures issued by FIFA to govern the organization, conduct, and administration of international football activities and stakeholders.
-
C.
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.
-
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.
UEFA Champions League match ball
The UEFA Champions League match ball is the official, specially designed and engineered football used in UEFA Champions League games, featuring distinctive star-themed graphics and meeting elite performance standards.
- F. None of above. chosen
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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:08 p.m.