Triple
T2614238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLI |
E58848
|
entity |
| Predicate | NFCChampionSeed |
P18175
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Super Bowl XLI, NFCChampionSeed, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NFCChampionSeed Context triple: [Super Bowl XLI, NFCChampionSeed, 1]
-
A.
NFCChampionRecord
Indicates that a team holds a record related to winning or appearing in NFC Championship games.
-
B.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
C.
NFCChampionRecordEnteringGame
Indicates the NFC team's season record at the time they enter a particular game, reflecting their performance up to but not including that game.
-
D.
NFCChampionshipOpponent
Indicates that one team was the opposing team faced in the NFC Championship game by the other team.
-
E.
eligibleSeedsPerConference
Indicates the specific tournament seed positions within each conference that qualify as eligible under the defined rules or criteria.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.