Triple
T20515290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991–92 Pittsburgh Penguins |
E503668
|
entity |
| Predicate | regularSeasonTies |
P140388
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [1991–92 Pittsburgh Penguins, regularSeasonTies, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonTies Context triple: [1991–92 Pittsburgh Penguins, regularSeasonTies, 9]
-
A.
regularSeasonWins
Indicates the number of games a team wins during the regular season of a competition.
-
B.
regularSeasonGamesPerTeam
Indicates the number of games each team plays during the regular season.
-
C.
regularSeasonLosses
Indicates the number of games a team lost during the regular season portion of a competition or league.
-
D.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
E.
regularSeasonScheduleType
Indicates the type or category of a regular season schedule that applies to a given competitive context.
- 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_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. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:36 a.m.