Triple
T28005259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League season (August–May) |
E707257
|
entity |
| Predicate | additionalSchedule |
P155121
|
FINISHED |
| Object | midweek fixtures |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: midweek fixtures | Statement: [Premier League season (August–May), additionalSchedule, midweek fixtures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalSchedule Context triple: [Premier League season (August–May), additionalSchedule, midweek fixtures]
-
A.
relatedSchedule
chosen
Indicates a relationship where one schedule is associated with, linked to, or derived from another schedule.
-
B.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
C.
definesScheduleFor
Indicates that one entity establishes or specifies the schedule according to which another entity operates or is organized.
-
D.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
E.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
- F. None of above.
Provenance (3 batches)
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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd4e25c81909b4a26577a4a5479 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:59 p.m.