Triple
T26664028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tele2 Arena |
E672130
|
entity |
| Predicate | maximumCapacityConcerts |
P67553
|
FINISHED |
| Object | approximately 40,000 |
—
|
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 40,000 | Statement: [Tele2 Arena, maximumCapacityConcerts, approximately 40,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCapacityConcerts Context triple: [Tele2 Arena, maximumCapacityConcerts, approximately 40,000]
-
A.
concertCapacity
chosen
Indicates the maximum number of people that can be accommodated at a concert event or venue.
-
B.
officialCapacity
Indicates that an action or relationship is undertaken or held by an entity in their formal, authorized, or institutional role rather than in a personal capacity.
-
C.
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.
-
D.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
E.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 3:08 a.m.