Triple
T2928494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992–93 NHL season |
E78901
|
entity |
| Predicate | scoringLeaderPoints |
P43995
|
FINISHED |
| Object | 160 |
—
|
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: 160 | Statement: [1992–93 NHL season, scoringLeaderPoints, 160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringLeaderPoints Context triple: [1992–93 NHL season, scoringLeaderPoints, 160]
-
A.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
B.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
C.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
D.
teamScoring
Indicates that a team achieves a score or points in a game, match, or competitive event.
-
E.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97ff0ddc8190acba9863bbe4f54b |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.