Triple
T3270714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLV |
E68639
|
entity |
| Predicate | PittsburghSteelersSuperBowlAppearancesTotalAfterGame |
P7566
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Super Bowl XLV, PittsburghSteelersSuperBowlAppearancesTotalAfterGame, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PittsburghSteelersSuperBowlAppearancesTotalAfterGame Context triple: [Super Bowl XLV, PittsburghSteelersSuperBowlAppearancesTotalAfterGame, 8]
-
A.
SuperBowlAppearances
chosen
Indicates the number of times an entity has participated in a Super Bowl game.
-
B.
SuperBowlAppearance
Indicates that an entity (typically a team or player) has participated in at least one Super Bowl game.
-
C.
BuffaloBillsConsecutiveSuperBowlAppearancesNumber
Indicates the number of consecutive Super Bowl appearances made by the Buffalo Bills.
-
D.
appearedInSuperBowl
Indicates that the entity participated as a player, coach, or key contributor in at least one Super Bowl game.
-
E.
yearOfSuperBowlAppearance
Indicates the specific calendar year in which a given team appeared in a particular Super Bowl.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff349148190beae8c0994b7ad83 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.