Triple
T21182286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1930–31 NHL season |
E521980
|
entity |
| Predicate | mostPointsNumber |
P29667
|
FINISHED |
| Object | 77 |
—
|
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: 77 | Statement: [1930–31 NHL season, mostPointsNumber, 77]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostPointsNumber Context triple: [1930–31 NHL season, mostPointsNumber, 77]
-
A.
corePointsMaximum
Indicates the maximum number of core points that can be assigned, accumulated, or recognized within a given system or context.
-
B.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
C.
hasHighestPoints
Indicates that the subject entity possesses the greatest number of points compared to all relevant others in the given context.
-
D.
mostWinsByPlayerCount
Indicates the maximum number of wins achieved by any single player within the considered set or context.
-
E.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:04 p.m.