Triple
T30577076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 Stanley Cup Finals |
E778277
|
entity |
| Predicate | opponentNotablePlayer |
P103928
|
FINISHED |
| Object | Bobby Clarke |
—
|
NE NERFINISHED |
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: Bobby Clarke | Statement: [1980 Stanley Cup Finals, opponentNotablePlayer, Bobby Clarke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentNotablePlayer Context triple: [1980 Stanley Cup Finals, opponentNotablePlayer, Bobby Clarke]
-
A.
notableOpponentTeamMember
chosen
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
B.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
C.
notableTeammate
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
D.
hasNotablePlayer
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.
-
E.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game of a competition.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:22 p.m.