Triple
T8027547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 NHL season |
E186892
|
entity |
| Predicate | topScorerGamesPlayed |
P80656
|
FINISHED |
| Object | 56 |
—
|
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: 56 | Statement: [2020–21 NHL season, topScorerGamesPlayed, 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topScorerGamesPlayed Context triple: [2020–21 NHL season, topScorerGamesPlayed, 56]
-
A.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
B.
topScorerPoints
Indicates the number of points scored by the top-scoring entity in a given context or event.
-
C.
mostTriesScoredByPlayer
Indicates that the referenced player holds the record for scoring the highest number of tries, typically within a specified competition, season, or context.
-
D.
mostGamesWonBy
Indicates that one entity holds the record for having won the greatest number of games compared to others in a given context.
-
E.
rankAllTimeGoals
Indicates a relationship that orders entities based on the total number of goals they have scored across all time.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.