Triple
T6360530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993–94 NHL season |
E143095
|
entity |
| Predicate | pointsLeaderTotalPoints |
P43995
|
FINISHED |
| Object | 130 |
—
|
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: 130 | Statement: [1993–94 NHL season, pointsLeaderTotalPoints, 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsLeaderTotalPoints Context triple: [1993–94 NHL season, pointsLeaderTotalPoints, 130]
-
A.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
B.
scoringLeaderPoints
chosen
Indicates the number of points scored by the leading scorer in a game, season, or competition.
-
C.
topScorerPoints
Indicates the number of points scored by the top-scoring entity in a given context or event.
-
D.
totalPointsScored
Indicates the total number of points accumulated or scored by an entity over a defined period, event, or context.
-
E.
scoringLeaderAssists
Indicates that the entity identified as the scoring leader in a game or season also recorded the most assists (or a specified number of assists) in that context.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f8758081909c5ce40abf57dd2c |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.