Triple
T18770296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers K-Rock Centre |
E458999
|
entity |
| Predicate | isPrimarilyUsedBy |
P40071
|
FINISHED |
| Object | ice hockey teams |
—
|
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: ice hockey teams | Statement: [Rogers K-Rock Centre, isPrimarilyUsedBy, ice hockey teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarilyUsedBy Context triple: [Rogers K-Rock Centre, isPrimarilyUsedBy, ice hockey teams]
-
A.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
primarilyUsedBy
chosen
Indicates that something is mainly or most commonly used by a particular entity or group.
-
C.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
D.
mainlyUses
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d8782b4819080513fb46798c4db |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.