Triple
T37981443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggie Leach |
E947558
|
entity |
| Predicate | notablePlayoffGoalsSeason |
P7472
|
FINISHED |
| Object | 1975–76 NHL playoffs |
E947557
|
NE 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: 1975–76 NHL playoffs | Statement: [Reggie Leach, notablePlayoffGoalsSeason, 1975–76 NHL playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayoffGoalsSeason Context triple: [Reggie Leach, notablePlayoffGoalsSeason, 1975–76 NHL playoffs]
-
A.
scoredGoalSeason
Indicates that an entity scored a goal during a specified season.
-
B.
notablePlayoffStatistic
chosen
Indicates that there exists a significant or distinguished statistical achievement associated with an entity’s performance in playoff competition.
-
C.
singleSeasonGoalsHigh
Indicates that an entity achieved a notably high number of goals within a single season.
-
D.
seasonGoalsRecordSeason
Indicates the specific season in which a particular season goals record was achieved or is valid.
-
E.
playoffAchievement
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
- F. None of above.
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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412cb20cc481909a55c601401f4e57 |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.