Triple
T3397824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Repertory Theatre |
E71571
|
entity |
| Predicate | hasMainAuditoriumCapacity |
P2491
|
FINISHED |
| Object | approximately 800 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: approximately 800 seats | Statement: [Birmingham Repertory Theatre, hasMainAuditoriumCapacity, approximately 800 seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAuditoriumCapacity Context triple: [Birmingham Repertory Theatre, hasMainAuditoriumCapacity, approximately 800 seats]
-
A.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
B.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
C.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
D.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
E.
hasMainHallType
Indicates the specific category or kind of main hall associated with an 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c5816881909f91e6e9b81d29e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.