Triple
T2404121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XIX |
E50234
|
entity |
| Predicate | seasonRecordOfLosingTeam |
P21379
|
FINISHED |
| Object | Miami Dolphins 16–3 overall |
—
|
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: Miami Dolphins 16–3 overall | Statement: [Super Bowl XIX, seasonRecordOfLosingTeam, Miami Dolphins 16–3 overall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecordOfLosingTeam Context triple: [Super Bowl XIX, seasonRecordOfLosingTeam, Miami Dolphins 16–3 overall]
-
A.
seasonRecordLosses
Indicates the number of games a team lost during a specific season.
-
B.
regularSeasonLosses
Indicates the number of games a team lost during the regular season portion of a competition or league.
-
C.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
D.
postseasonSeriesLoser
Indicates that one team or competitor lost a particular postseason series to another team or competitor.
-
E.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:58 p.m.