Triple
T38057282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA World Cup matches |
E950238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FIFA competition fixture |
C22973
|
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: FIFA competition fixture Context triple: [FIFA World Cup matches, instanceOf, FIFA competition fixture]
-
A.
international football fixture
chosen
An international football fixture is a scheduled match between two national football teams, organized under the authority of governing bodies such as FIFA or continental confederations, typically for competition, qualification, or friendly purposes.
-
B.
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.
-
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.
FIFA trigramme
A FIFA trigramme is the unique three-letter code assigned by FIFA to identify a national football association or its representative teams in official competitions and records.
-
E.
association football skills competition
An association football skills competition is an organized event where players perform and are judged on specific technical abilities—such as dribbling, shooting, passing, and ball control—often in timed or scored challenges separate from regular match play.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.