Triple
T28580661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 New Orleans Saints season |
E723364
|
entity |
| Predicate | conferenceChampionshipResult |
P72340
|
FINISHED |
| Object | win |
—
|
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: win | Statement: [2009 New Orleans Saints season, conferenceChampionshipResult, win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceChampionshipResult Context triple: [2009 New Orleans Saints season, conferenceChampionshipResult, win]
-
A.
championshipOutcome
chosen
Indicates the result or final standing of a competitor or team in a championship event.
-
B.
conferenceChampionshipGame
Indicates a game that determines the champion of a specific sports conference.
-
C.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
D.
subsequentChampionshipResult
Indicates the outcome or result of a championship that occurs immediately after a referenced earlier championship.
-
E.
competitionResult
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 4:14 a.m.