Triple
T26832263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbotsford Heat |
E675529
|
entity |
| Predicate | operatedAsAHLFranchiseOf |
P68788
|
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: [Abbotsford Heat, operatedAsAHLFranchiseOf, Calgary Flames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsAHLFranchiseOf Context triple: [Abbotsford Heat, operatedAsAHLFranchiseOf, Calgary Flames]
-
A.
formerAHLFranchiseOf
chosen
Indicates that one entity was previously an American Hockey League (AHL) franchise of the other entity, but no longer holds that status.
-
B.
foundedAsAHLFranchise
Indicates that an organization or team was originally established as a franchise in the American Hockey League (AHL).
-
C.
foundedAsCurrentAHLFranchise
Indicates that an entity was originally established as the current franchise of the American Hockey League (AHL).
-
D.
AHLfranchiseRelocatedFrom
Indicates that an AHL franchise moved its operations from one specified location or team identity to another.
-
E.
AHLTeam
Indicates that an entity is a team that competes in the American Hockey League (AHL).
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 27, 2026, 5:02 a.m.