Triple
T23524640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miikka Kiprusoff |
E574598
|
entity |
| Predicate | primaryNHLTeam |
P81681
|
FINISHED |
| Object | Calgary Flames |
—
|
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: Calgary Flames | Statement: [Miikka Kiprusoff, primaryNHLTeam, Calgary Flames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNHLTeam Context triple: [Miikka Kiprusoff, primaryNHLTeam, Calgary Flames]
-
A.
primaryTeam
Indicates that one entity is the main or principal team associated with another entity, such as a person, project, or organization.
-
B.
primaryTeams
Indicates that one or more teams are the main or principal teams associated with a given entity.
-
C.
HallOfFamePrimaryTeam
Indicates the team most prominently associated with an individual's Hall of Fame recognition, typically considered their primary or defining team.
-
D.
hostTeamFranchise
Indicates that a team franchise is serving as the host team in a given game or event.
-
E.
NHLPrimaryTeam
chosen
Indicates that one entity is the primary NHL team associated with, or having principal affiliation to, another entity (such as a player, coach, or staff member).
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac72bfb88190b7da3837e66e851c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.