Triple
T12855928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Steelers–Philadelphia Eagles rivalry |
E307453
|
entity |
| Predicate | EaglesSuperBowlTitles |
P5809
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Pittsburgh Steelers–Philadelphia Eagles rivalry, EaglesSuperBowlTitles, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EaglesSuperBowlTitles Context triple: [Pittsburgh Steelers–Philadelphia Eagles rivalry, EaglesSuperBowlTitles, 1]
-
A.
EaglesSuperBowlAppearanceNumber
Indicates the ordinal number of times the Philadelphia Eagles have appeared in a Super Bowl.
-
B.
EaglesFirstSuperBowlTitle
Indicates that the event represents the Philadelphia Eagles winning their first Super Bowl championship title.
-
C.
EaglesPreviousSeasonSuperBowlAppearance
Indicates that the Philadelphia Eagles’ immediately preceding NFL season included an appearance in the Super Bowl.
-
D.
PittsburghSteelersConsecutiveSuperBowls
Indicates that the Pittsburgh Steelers appeared in or won Super Bowls in consecutive seasons.
-
E.
team2SuperBowlTitles
chosen
Indicates the number of Super Bowl championships won by the second team in a given context.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.