Triple
T28580662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 New Orleans Saints season |
E723364
|
entity |
| Predicate | conferenceChampionshipScore |
P119380
|
FINISHED |
| Object | 31–28 OT |
—
|
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: 31–28 OT | Statement: [2009 New Orleans Saints season, conferenceChampionshipScore, 31–28 OT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChampionshipScore Context triple: [2009 New Orleans Saints season, conferenceChampionshipScore, 31–28 OT]
-
A.
championshipGameScore
Indicates the final score achieved by each participant in a championship game.
-
B.
postseasonMeetingScore
chosen
Indicates the score or outcome of a competitive meeting (such as a game or match) that takes place during a postseason phase.
-
C.
conferenceChampionshipGame
Indicates a game that determines the champion of a specific sports conference.
-
D.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
-
E.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 4:14 a.m.