Triple
T3527645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XII |
E74578
|
entity |
| Predicate | seasonRecordWinningTeam |
P21379
|
FINISHED |
| Object | 12–2 |
—
|
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: 12–2 | Statement: [Super Bowl XII, seasonRecordWinningTeam, 12–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecordWinningTeam Context triple: [Super Bowl XII, seasonRecordWinningTeam, 12–2]
-
A.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
-
B.
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).
-
C.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
D.
bestRegularSeasonRecord
Indicates that an entity (typically a team) achieved the highest overall performance record during the regular season compared to all others in the same competition.
-
E.
runnerUpRegularSeasonRecord
Indicates the regular season performance record (such as wins and losses) of the team that finished as runner-up.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6d099c8190b2b1e65a56e52089 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.