Triple
T605884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl LII |
E11592
|
entity |
| Predicate | EaglesRegularSeasonRecord |
P17021
|
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 LII, EaglesRegularSeasonRecord, 13–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EaglesRegularSeasonRecord Context triple: [Super Bowl LII, EaglesRegularSeasonRecord, 13–3]
-
A.
ALTeamRegularSeasonRecord
Indicates the relationship that specifies a team's win–loss record during the American League regular season.
-
B.
EaglesRecordEnteringGame
Indicates the statistical record or performance status of the Eagles team as it stood immediately before a specific game began.
-
C.
NLTeamRegularSeasonRecord
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
-
D.
GiantsRegularSeasonRecordEnteringGame
Indicates the Giants’ cumulative regular-season win–loss record at the time a particular game begins.
-
E.
EaglesSuperBowlAppearanceNumber
Indicates the ordinal number of times the Philadelphia Eagles have appeared in a Super Bowl.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.