Triple
T2248545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXII |
E49561
|
entity |
| Predicate | losingTeamRecordEnteringGame |
P36482
|
FINISHED |
| Object | 10–4–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: 10–4–1 | Statement: [Super Bowl XXII, losingTeamRecordEnteringGame, 10–4–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: losingTeamRecordEnteringGame Context triple: [Super Bowl XXII, losingTeamRecordEnteringGame, 10–4–1]
-
A.
homeTeamRecordEnteringGame
Indicates the win-loss (and possibly tie) record that the home team had prior to the start of the game.
-
B.
losingLeagueTeam
Indicates that a team is the one that lost in a particular league game or competition.
-
C.
losingTeamNickname
Indicates the nickname of the team that lost in a given game or competition.
-
D.
losingTeamLeague
Indicates that a team is the losing side in a game or match within a particular league.
-
E.
losingTeamCity
Indicates the city associated with the team that lost a particular game or competition.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ed5c38819080b45ea398fb59f2 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.