Triple
T3435874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Oregon–Oregon State football game |
E72449
|
entity |
| Predicate | seasonWeek |
P48238
|
FINISHED |
| Object | final week of 2008 regular 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: final week of 2008 regular season | Statement: [2008 Oregon–Oregon State football game, seasonWeek, final week of 2008 regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonWeek Context triple: [2008 Oregon–Oregon State football game, seasonWeek, final week of 2008 regular season]
-
A.
seasonSchedule
Indicates the planned timing and sequence of events, activities, or occurrences within a specific season.
-
B.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
C.
SuperBowlSeason
Indicates that a particular season is identified as the one in which a given Super Bowl game is played or associated.
-
D.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
E.
seasonAfter
Indicates that one season occurs chronologically immediately after another season in a sequence.
- F. None of above. chosen
Provenance (4 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f2e4b4819085336fb539daf3c7 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.