Triple
T24971453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 AFC Wild Card Game |
E624899
|
entity |
| Predicate | jetsNextPlayoffOpponent |
P98660
|
FINISHED |
| Object | San Diego Chargers |
—
|
NE NERFINISHED |
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: San Diego Chargers | Statement: [2009 AFC Wild Card Game, jetsNextPlayoffOpponent, San Diego Chargers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jetsNextPlayoffOpponent Context triple: [2009 AFC Wild Card Game, jetsNextPlayoffOpponent, San Diego Chargers]
-
A.
playoffOpponent
chosen
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
B.
homeTeamNextOpponent
Indicates that a given team is scheduled to play against a specified opponent in its next home game.
-
C.
nextPlayoffs
Indicates that one event or season directly follows another in the sequence of playoff competitions.
-
D.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
-
E.
awayTeamPlayoffPath
Indicates the sequence of playoff matchups and results that the away team must navigate or has navigated in a tournament or postseason bracket.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:01 a.m.