Triple
T18271252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League fixtures |
E437619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | football fixtures list |
C7840
|
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 fixtures list Context triple: [Premier League fixtures, instanceOf, football fixtures list]
-
A.
international football fixture
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.
association football match collection
chosen
A collection of association football matches is an organized set of individual games grouped for a specific purpose, such as a season, tournament, or analytical dataset.
-
C.
rugby league home fixtures context
The rugby league home fixtures context represents the environment, conditions, and associated information surrounding a team's scheduled home matches, including venue details, dates, opponents, and relevant logistical or competitive factors.
-
D.
representative rugby league fixture
A representative rugby league fixture is a competitive match in which selected players from clubs or regions form special teams (such as state, national, or all-star sides) to compete at a higher representative level than regular club competition.
-
E.
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.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.