Triple
T32791687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purple Raiders football |
E838643
|
entity |
| Predicate | playoffStreak |
P2486
|
FINISHED |
| Object | 1990s–2010s |
—
|
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: 1990s–2010s | Statement: [Purple Raiders football, playoffStreak, 1990s–2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffStreak Context triple: [Purple Raiders football, playoffStreak, 1990s–2010s]
-
A.
playoffRecord
Indicates the win-loss performance of an entity (such as a team or player) in postseason or playoff competitions.
-
B.
playoffAppearances
chosen
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
-
C.
endedPlayoffDrought
Indicates that a team or participant has successfully qualified for the playoffs after a prolonged period of failing to do so.
-
D.
playoffHistory
Indicates a relationship detailing an entity’s record, participation, or performance across one or more playoff competitions or seasons.
-
E.
playoffAchievement
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.