Triple
T16398524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Stanley Cup Finals |
E398247
|
entity |
| Predicate | notableGame4Length |
P15428
|
FINISHED |
| Object | triple overtime |
—
|
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: triple overtime | Statement: [1996 Stanley Cup Finals, notableGame4Length, triple overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGame4Length Context triple: [1996 Stanley Cup Finals, notableGame4Length, triple overtime]
-
A.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
C.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
D.
gameLength
chosen
Indicates the duration or total length of a game, typically measured in time or turns.
-
E.
notableConsoleGame
Indicates that a game is recognized as a significant or prominent title released for a particular video game console.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cdc62481909de144b09a921e63 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.