Triple
T11698211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMO Harris Bradley Center |
E278050
|
entity |
| Predicate | capacityHockey |
P3606
|
FINISHED |
| Object | about 17,800 |
—
|
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: about 17,800 | Statement: [BMO Harris Bradley Center, capacityHockey, about 17,800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityHockey Context triple: [BMO Harris Bradley Center, capacityHockey, about 17,800]
-
A.
homeArenaCapacity
chosen
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
B.
mainIceHockeyVenue
Indicates that a location serves as the primary venue where a team or organization regularly plays its ice hockey games.
-
C.
numberOfPlayersOnIcePerTeam
Indicates the count of players from a single team who are on the ice at the same time during play.
-
D.
infieldCapacity
Indicates the maximum number of entities that can be accommodated within a defined infield area or region.
-
E.
officialCapacities
Indicates that the relationship or action is performed in an entity’s formal, authorized, or institutional role rather than in a personal or informal capacity.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.