Triple
T27483775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richfield Avenue |
E693676
|
entity |
| Predicate | hasVenueCapacity |
P103582
|
FINISHED |
| Object | approximately 90000 people |
—
|
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 90000 people | Statement: [Richfield Avenue, hasVenueCapacity, approximately 90000 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVenueCapacity Context triple: [Richfield Avenue, hasVenueCapacity, approximately 90000 people]
-
A.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
B.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
C.
venueCapacityApproximate
chosen
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
D.
concertCapacity
Indicates the maximum number of people that can be accommodated at a concert event or venue.
-
E.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 1:01 p.m.