Triple
T1861128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Andel Arena |
E34813
|
entity |
| Predicate | seatingCapacityIceHockey |
P2491
|
FINISHED |
| Object | approximately 10,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: approximately 10,800 | Statement: [Van Andel Arena, seatingCapacityIceHockey, approximately 10,800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityIceHockey Context triple: [Van Andel Arena, seatingCapacityIceHockey, approximately 10,800]
-
A.
numberOfPlayersOnIcePerTeam
Indicates the count of players from a single team who are on the ice at the same time during play.
-
B.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
D.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
-
E.
iceSurface
Indicates that something is located on, in contact with, or forming the surface of ice.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.