Triple
T28700792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Olympic Organizing Committee |
E729543
|
entity |
| Predicate | eventProvinceOrState |
P26493
|
FINISHED |
| Object | Alberta |
—
|
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: Alberta | Statement: [Calgary Olympic Organizing Committee, eventProvinceOrState, Alberta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventProvinceOrState Context triple: [Calgary Olympic Organizing Committee, eventProvinceOrState, Alberta]
-
A.
teamProvinceOrState
Indicates that a team is located in, or associated with, a particular province or state.
-
B.
provinceName
Indicates that a province entity is associated with its specific name as a textual label.
-
C.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
D.
hostProvinceOrState
chosen
Indicates that one administrative province or state serves as the host or location for another entity, such as an event, organization, or facility.
-
E.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 5:42 a.m.