Triple
T36014438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football on ESPN |
E1041798
|
entity |
| Predicate | seasonalCoverage |
P65354
|
FINISHED |
| Object | college football season |
—
|
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: college football season | Statement: [College Football on ESPN, seasonalCoverage, college football season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalCoverage Context triple: [College Football on ESPN, seasonalCoverage, college football season]
-
A.
typicalSeasonCovered
chosen
Indicates the season or time of year that is most commonly encompassed or represented by something.
-
B.
seasonalCategory
Indicates that something is associated with, classified by, or relevant to a particular season or time of year.
-
C.
seasonalValidity
Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
-
D.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
E.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:07 p.m.