Triple
T4632378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXXIV |
E101445
|
entity |
| Predicate | ramsRecordEnteringGame |
P57852
|
FINISHED |
| Object | 13–3 |
—
|
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–3 | Statement: [Super Bowl XXXIV, ramsRecordEnteringGame, 13–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ramsRecordEnteringGame Context triple: [Super Bowl XXXIV, ramsRecordEnteringGame, 13–3]
-
A.
BillsRecordEnteringGame
Indicates the statistical record or performance metrics that the Bills team has accumulated prior to the start of a particular game.
-
B.
DolphinsRecordEnteringGame
Indicates that a record is made of the Dolphins team entering a particular game or matchup.
-
C.
winningTeamLeagueRecordEnteringGame
Indicates the win-loss (and possibly tie) record that the winning team had in its league before the game was played.
-
D.
losingTeamRecordEnteringGame
Indicates that the team’s win-loss record prior to the game was a losing record (more losses than wins) entering that specific game.
-
E.
EaglesRecordEnteringGame
Indicates the statistical record or performance status of the Eagles team as it stood immediately before a specific game began.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a342ffc8190a911d0598ed230bb |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.