Triple
T22959815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Sports and Entertainment Corporation |
E570861
|
entity |
| Predicate | cityOfPrimaryOperations |
P14306
|
FINISHED |
| Object | Calgary |
—
|
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 | Statement: [Calgary Sports and Entertainment Corporation, cityOfPrimaryOperations, Calgary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfPrimaryOperations Context triple: [Calgary Sports and Entertainment Corporation, cityOfPrimaryOperations, Calgary]
-
A.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
B.
notableCityOfOperation
chosen
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
-
C.
cityOfMajorPresence
Indicates that an entity has a significant or primary operational, demographic, or functional presence in the specified city.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.