Triple
T14449997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Pac-12 Conference football season |
E358304
|
entity |
| Predicate | returnToPlayAnnouncementDate |
P429
|
FINISHED |
| Object | 2020-09-24 |
—
|
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: 2020-09-24 | Statement: [2020 Pac-12 Conference football season, returnToPlayAnnouncementDate, 2020-09-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnToPlayAnnouncementDate Context triple: [2020 Pac-12 Conference football season, returnToPlayAnnouncementDate, 2020-09-24]
-
A.
hasReturnedToPlayIn
Indicates that an entity has resumed participating or performing in a particular event, context, or location after a period of absence.
-
B.
returnToPlayCompetitionFor
Indicates that an entity resumes participating in a competition or match on behalf of another entity (such as a team, club, or organization).
-
C.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
D.
typicalAnnouncementTime
Indicates the usual or standard time at which an announcement is made or expected to occur.
-
E.
announcedAfter
Indicates that one announcement occurred later in time than another specified announcement.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916139888190be219678e29a2a3a |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.