Triple
T20515302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991–92 Pittsburgh Penguins |
E503668
|
entity |
| Predicate | playoffSeriesWon |
P36149
|
FINISHED |
| Object | vs Washington Capitals |
—
|
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: vs Washington Capitals | Statement: [1991–92 Pittsburgh Penguins, playoffSeriesWon, vs Washington Capitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffSeriesWon Context triple: [1991–92 Pittsburgh Penguins, playoffSeriesWon, vs Washington Capitals]
-
A.
hasWonSeries
Indicates that one entity has achieved overall victory in a multi-game or multi-event series against another entity.
-
B.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
C.
postseasonSeriesWinner
chosen
Indicates which competitor or team won a particular postseason series in a sports or competitive context.
-
D.
playoffAchievement
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
-
E.
wonChampionshipInSeries
Indicates that an entity secured a championship title during a specified series or sequence of competitive events.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4133048190abb777be4b65c2c4 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.