Triple
T3366396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XIV |
E70845
|
entity |
| Predicate | PittsburghSteelersConsecutiveSuperBowls |
P47598
|
FINISHED |
| Object | 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: 2 | Statement: [Super Bowl XIV, PittsburghSteelersConsecutiveSuperBowls, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PittsburghSteelersConsecutiveSuperBowls Context triple: [Super Bowl XIV, PittsburghSteelersConsecutiveSuperBowls, 2]
-
A.
BuffaloBillsConsecutiveSuperBowlAppearancesNumber
Indicates the number of consecutive Super Bowl appearances made by the Buffalo Bills.
-
B.
seahawksConsecutiveSuperBowlAppearancesNumber
Indicates the number of consecutive seasons in which the Seahawks appeared in the Super Bowl.
-
C.
wonSuperBowlWith
Indicates that one entity (typically a player, coach, or team member) achieved a Super Bowl victory while being part of a specific team.
-
D.
appearedInSuperBowl
Indicates that the entity participated as a player, coach, or key contributor in at least one Super Bowl game.
-
E.
SuperBowlAppearances
Indicates the number of times an entity has participated in a Super Bowl game.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb287a30c8190b4c40091675c94fb |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:13 p.m.