Triple
T28580658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 New Orleans Saints season |
E723364
|
entity |
| Predicate | reachedConferenceChampionshipGame |
P165465
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2009 New Orleans Saints season, reachedConferenceChampionshipGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedConferenceChampionshipGame Context triple: [2009 New Orleans Saints season, reachedConferenceChampionshipGame, true]
-
A.
hasReachedNationalChampionshipGame
Indicates that an entity has advanced to and participated in the final game of a national championship competition.
-
B.
reachedPlayoffs
Indicates that a team or competitor successfully qualified for and participated in the playoff stage of a competition.
-
C.
playsChampionshipGame
Indicates that an entity participates as a competitor in a championship-level game or match.
-
D.
hasChampionshipGames
Indicates that an entity includes, hosts, or is associated with one or more championship-level games or matches.
-
E.
reachedNBAGLeagueFinals
Indicates that an entity has advanced to and competed in the NBA G League Finals series in a given season.
- F. None of above. chosen
Provenance (4 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_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:14 a.m.