Triple
T25926040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Wranglers |
E653305
|
entity |
| Predicate | playsIceHockeyIn |
P160952
|
FINISHED |
| Object | Scotiabank Saddledome |
—
|
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: Scotiabank Saddledome | Statement: [Calgary Wranglers, playsIceHockeyIn, Scotiabank Saddledome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsIceHockeyIn Context triple: [Calgary Wranglers, playsIceHockeyIn, Scotiabank Saddledome]
-
A.
playedInKHLTeam
Indicates that a person has been a player for a specific team in the Kontinental Hockey League (KHL).
-
B.
iceHockeyTeamOf
Indicates that one entity is the ice hockey team to which the other entity belongs or is affiliated.
-
C.
playedCollegeHockeyFor
Indicates that a person was a member of and competed for a particular college or university’s ice hockey team.
-
D.
playsIceHockeyCode
Indicates that one entity participates in ice hockey under the specific code, ruleset, or organizational classification represented by the other entity.
-
E.
playedJuniorHockeyIn
Indicates that a person participated in junior-level ice hockey for a team or in a league located in a specified place.
- F. None of above. chosen
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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60dfaeebc8190ac01d3a0030acf55 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c68b02c8190870758d79cdec68b |
completed | May 2, 2026, 2:38 p.m. |
Created at: April 22, 2026, 8:35 a.m.