Triple
T30704418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 Stanley Cup Finals |
E781711
|
entity |
| Predicate | notablePlayerOilers |
P127323
|
FINISHED |
| Object | Wayne Gretzky |
E19557
|
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: Wayne Gretzky | Statement: [1983 Stanley Cup Finals, notablePlayerOilers, Wayne Gretzky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerOilers Context triple: [1983 Stanley Cup Finals, notablePlayerOilers, Wayne Gretzky]
-
A.
notableOilersStars
chosen
Indicates that the subject is a notable or standout star associated with the Edmonton Oilers hockey team.
-
B.
notablePlayerDallasStars
Indicates that a person is a notable or prominent player for the Dallas Stars hockey team.
-
C.
notablePlayerWesternConference
Indicates that a player is recognized as a notable or standout player within the NBA’s Western Conference.
-
D.
quarterbackOfOilers
Indicates that one entity serves as the quarterback for the football team known as the Oilers.
-
E.
notableDefenseman
Indicates that a person plays or played the position of defenseman in a sport and is recognized as particularly prominent, skilled, or distinguished in that role.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b074dfda88190bfc8521eb15f3ef7 |
completed | June 11, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:35 p.m.