Triple
T28040540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macerata Opera Festival |
E708525
|
entity |
| Predicate | hasMainVenueCapacity |
P103582
|
FINISHED |
| Object | about 2500 seats |
—
|
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: about 2500 seats | Statement: [Macerata Opera Festival, hasMainVenueCapacity, about 2500 seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainVenueCapacity Context triple: [Macerata Opera Festival, hasMainVenueCapacity, about 2500 seats]
-
A.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
B.
venueCapacityApproximate
chosen
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
E.
hasVenueCapacityInfluence
Indicates that one entity affects or determines the capacity (e.g., size or occupancy limit) of a venue associated with another entity.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 27, 2026, 8:25 p.m.