Triple
T16343684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PostFinance Arena |
E396873
|
entity |
| Predicate | hasLargestStandingRoomInEuropeForIceHockey |
P123047
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PostFinance Arena, hasLargestStandingRoomInEuropeForIceHockey, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargestStandingRoomInEuropeForIceHockey Context triple: [PostFinance Arena, hasLargestStandingRoomInEuropeForIceHockey, true]
-
A.
mainIceHockeyVenue
Indicates that a location serves as the primary venue where a team or organization regularly plays its ice hockey games.
-
B.
hasIceHockeyCapacity
Indicates that an entity is capable of hosting or accommodating ice hockey activities, such as games or practices.
-
C.
mainIndoorArena
Indicates that one entity serves as the primary indoor arena or main covered venue associated with another entity.
-
D.
largestVenueOf
Indicates that one venue is the largest (typically by capacity, area, or scale) among a specified set or within a particular context.
-
E.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
- F. None of above. chosen
Provenance (4 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0c90e0819086f0a80a10cd79f3 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.