Triple
T31384172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geva Theatre Center |
E800550
|
entity |
| Predicate | secondStageSeatingCapacityApprox |
P2491
|
FINISHED |
| Object | 180 |
—
|
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: 180 | Statement: [Geva Theatre Center, secondStageSeatingCapacityApprox, 180]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondStageSeatingCapacityApprox Context triple: [Geva Theatre Center, secondStageSeatingCapacityApprox, 180]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
secondPartySeats
Indicates that a second party assigns or provides seating or seats to another entity.
-
C.
hasSecondSeat
Indicates that an entity possesses or includes a secondary seat in addition to a primary one.
-
D.
reducedSeatingCapacityFrom
Indicates that an entity has a smaller seating capacity than it previously had, with the prior capacity specified by the related entity.
-
E.
typicalSeatingCapacityLowerBound
Indicates the minimum number of seats that an entity is typically designed or expected to provide.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 9:19 p.m.