Triple
T657296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice "Rocket" Richard Trophy |
E11674
|
entity |
| Predicate | mostWinsNumber |
P12883
|
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: [Maurice "Rocket" Richard Trophy, mostWinsNumber, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostWinsNumber Context triple: [Maurice "Rocket" Richard Trophy, mostWinsNumber, 9]
-
A.
mostOverallWinsHolder
Indicates that the subject is the entity holding the highest total number of wins overall, compared to all other relevant entities.
-
B.
mostWinsByPlayerCount
chosen
Indicates the maximum number of wins achieved by any single player within the considered set or context.
-
C.
mostOverallWinsRecord
Indicates that the subject holds the record for having the greatest total number of wins compared to all others in the relevant context.
-
D.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
E.
mostConsecutiveWinsPlayer
Indicates the player who holds the record for the highest number of consecutive wins within a given context or competition.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa55e048190bd9913c6c31772d0 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.