Triple
T7822362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Stadium |
E181161
|
entity |
| Predicate | capacityDuringEvent |
P79202
|
FINISHED |
| Object | around 30,000 (Birmingham 2022) |
—
|
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: around 30,000 (Birmingham 2022) | Statement: [Alexander Stadium, capacityDuringEvent, around 30,000 (Birmingham 2022)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityDuringEvent Context triple: [Alexander Stadium, capacityDuringEvent, around 30,000 (Birmingham 2022)]
-
A.
capacityDuringOlympics
Indicates the seating or usage capacity of a venue, facility, or service specifically during the Olympic Games period.
-
B.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
concertCapacity
Indicates the maximum number of people that can be accommodated at a concert event or venue.
-
E.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa095d7081908b3e492ce58b5d5f |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:41 p.m.