Triple
T28580646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 New Orleans Saints season |
E723364
|
entity |
| Predicate | startedSeasonWithWinningStreak |
P8065
|
FINISHED |
| Object | 13 games |
—
|
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: 13 games | Statement: [2009 New Orleans Saints season, startedSeasonWithWinningStreak, 13 games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startedSeasonWithWinningStreak Context triple: [2009 New Orleans Saints season, startedSeasonWithWinningStreak, 13 games]
-
A.
longestWinningStreakStart
Indicates the point in time or sequence at which an entity’s longest continuous winning streak begins.
-
B.
winningStreakEndDate
Indicates the date on which an entity’s winning streak comes to an end.
-
C.
consecutiveWinsInSeason
chosen
Indicates that one entity achieved a specified number of back-to-back victories within a single season.
-
D.
consecutiveWinningSeasons
Indicates that an entity (such as a team or individual) has achieved winning seasons in back-to-back or uninterrupted consecutive years.
-
E.
hittingStreakStartDate
Indicates the date on which a continuous sequence of successful hits (a hitting streak) begins.
- 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_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 4:14 a.m.