Triple
T27119567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Warriors |
E686956
|
entity |
| Predicate | homeArenaUse |
P36718
|
FINISHED |
| Object | multi-purpose indoor arena |
—
|
LITERAL FINISHED |
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: multi-purpose indoor arena | Statement: [Vancouver Warriors, homeArenaUse, multi-purpose indoor arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeArenaUse Context triple: [Vancouver Warriors, homeArenaUse, multi-purpose indoor arena]
-
A.
homeArenaDuringUse
Indicates that a particular arena served as the primary home venue for an entity (such as a team or performer) during a specified period of use.
-
B.
homeArenaUsed
Indicates that a particular arena serves as the primary home venue for a team or organization.
-
C.
homeArenaUntil
Indicates that a particular venue served as an entity’s home arena up to a specified time or date.
-
D.
homeArenaFor
Indicates that a particular arena serves as the primary home venue for a specified sports team or organization.
-
E.
homeArenaType
chosen
Indicates the type or category of arena that serves as the primary home venue for an entity.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624421d188190a5356a4596df536e |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:58 a.m.