Triple
T14358219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 NFL season |
E356026
|
entity |
| Predicate | SteelersPlayoffSeed |
P113914
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [2005 NFL season, SteelersPlayoffSeed, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SteelersPlayoffSeed Context triple: [2005 NFL season, SteelersPlayoffSeed, 6]
-
A.
SteelersDivision
Indicates a relationship where an entity is identified as the NFL division in which the Pittsburgh Steelers team competes.
-
B.
SteelersConference
Indicates the conference within a sports league to which the Steelers team belongs.
-
C.
PittsburghSteelersNextSuperBowl
Indicates the event or outcome corresponding to the Pittsburgh Steelers’ next appearance in a Super Bowl game.
-
D.
PittsburghSteelersPreviousSuperBowl
Indicates that the referenced Super Bowl is the one the Pittsburgh Steelers participated in or won immediately before a given Super Bowl or point in time.
-
E.
SteelersChampionshipReputation
Indicates that an entity is recognized for having a strong reputation associated with the Pittsburgh Steelers’ championship success.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:15 a.m.