Triple
T23002015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPro Stadium |
E572655
|
entity |
| Predicate | hasSeatingCapacityOf |
P2491
|
FINISHED |
| Object | approximately 33,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 33,000 | Statement: [iPro Stadium, hasSeatingCapacityOf, approximately 33,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatingCapacityOf Context triple: [iPro Stadium, hasSeatingCapacityOf, approximately 33,000]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
seatCount
Indicates the number of seats associated with an entity, such as a venue, vehicle, or room.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
hasSeatingCapacityCategory
Indicates the classification of an entity based on the range or category of how many people it can seat.
-
E.
hasSeatingCapacityWithStanding
Indicates that an entity has a total seating capacity that explicitly includes standing room capacity as part of its overall accommodation.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18353d05481909abacb48a14ef21e |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.