Triple
T25000706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Stanley Cup championship |
E625710
|
entity |
| Predicate | decidingGameDate |
P158157
|
FINISHED |
| Object | 2019-06-12 |
—
|
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: 2019-06-12 | Statement: [2019 Stanley Cup championship, decidingGameDate, 2019-06-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingGameDate Context triple: [2019 Stanley Cup championship, decidingGameDate, 2019-06-12]
-
A.
game1Date
Indicates the calendar date on which the first game or match in a series takes place.
-
B.
typicalGameDate
Indicates the usual or standard calendar date on which a particular game is played or scheduled to occur.
-
C.
recordGameDate
Indicates that an entity logs or stores the date on which a particular game took place or is scheduled.
-
D.
game3Date
Indicates the calendar date on which the third game in a series or sequence takes place.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 6:04 a.m.