Triple
T28580660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 New Orleans Saints season |
E723364
|
entity |
| Predicate | conferenceChampionshipOpponent |
P98660
|
FINISHED |
| Object | Minnesota Vikings |
—
|
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: Minnesota Vikings | Statement: [2009 New Orleans Saints season, conferenceChampionshipOpponent, Minnesota Vikings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChampionshipOpponent Context triple: [2009 New Orleans Saints season, conferenceChampionshipOpponent, Minnesota Vikings]
-
A.
finalOpponentOf
Indicates that one entity serves as the last or ultimate opponent faced by another entity in a sequence of confrontations or competitions.
-
B.
finalOpponentTeam
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
C.
conferenceChampionshipGame
Indicates a game that determines the champion of a specific sports conference.
-
D.
playoffOpponent
chosen
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
E.
finalLeagueMatchOpponent
Indicates the opposing team or player faced in an entity’s final league match.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 4:14 a.m.