Triple
T30704414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 Stanley Cup Finals |
E781711
|
entity |
| Predicate | notablePlayerIslanders |
P9730
|
FINISHED |
| Object | Mike Bossy |
E35006
|
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: Mike Bossy | Statement: [1983 Stanley Cup Finals, notablePlayerIslanders, Mike Bossy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerIslanders Context triple: [1983 Stanley Cup Finals, notablePlayerIslanders, Mike Bossy]
-
A.
hasNotablePlayer
chosen
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
B.
notableCrossoverPlayer
Indicates that a player is notably recognized for successfully transitioning and performing in multiple distinct leagues, sports, or competitive domains.
-
C.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
D.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
E.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
- 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_6a2a1e0b73d88190a6e80588bb4ba543 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:35 p.m.