Triple
T28005258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League season (August–May) |
E707257
|
entity |
| Predicate | traditionalSchedule |
P3309
|
FINISHED |
| Object | weekend 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: weekend fixtures | Statement: [Premier League season (August–May), traditionalSchedule, weekend fixtures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSchedule Context triple: [Premier League season (August–May), traditionalSchedule, weekend fixtures]
-
A.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
C.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
-
D.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
E.
traditionalStructure
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 27, 2026, 7:59 p.m.