Triple
T31613982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccaneers |
E806704
|
entity |
| Predicate | footballProgramReinstatedYear |
P100976
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Buccaneers, footballProgramReinstatedYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballProgramReinstatedYear Context triple: [Buccaneers, footballProgramReinstatedYear, 2015]
-
A.
footballProgramDiscontinuedYear
Indicates the year in which a football program was officially discontinued or terminated.
-
B.
resumedVarsityPlay
Indicates that an individual has returned to participating in varsity-level play after a period of interruption or absence.
-
C.
playedForCollegeTeamUntil
Indicates that an individual was a member of and played for a specific college team up to (and including) a particular end date or season.
-
D.
establishedAsVarsityProgram
Indicates that an athletic or academic program was officially recognized and elevated to full varsity status within an institution.
-
E.
programReinstatement
chosen
Indicates that a previously discontinued, suspended, or inactive program has been restored to active status.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8a8e2e48190bfb58408029dd46a |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:38 p.m.