Triple
T28570033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Canada Cup |
E722787
|
entity |
| Predicate | hostArenas |
P76907
|
FINISHED |
| Object | Copps Coliseum |
—
|
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: Copps Coliseum | Statement: [1987 Canada Cup, hostArenas, Copps Coliseum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostArenas Context triple: [1987 Canada Cup, hostArenas, Copps Coliseum]
-
A.
hostArena
chosen
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
B.
hostPark
Indicates that an entity provides space or facilities for a park to be located or held within its area.
-
C.
hostsAward
Indicates that an entity organizes and presents an award event or ceremony for another entity.
-
D.
hostEmpire
Indicates that one entity serves as the imperial authority or ruling empire that hosts, controls, or encompasses another entity.
-
E.
homeArenaUntil
Indicates that a particular venue served as an entity’s home arena up to a specified time or date.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f650924b1c8190978fca7cb865f32a |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:09 a.m.