Triple
T11555391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uris Theatre |
E274005
|
entity |
| Predicate | hasLargeSeatingCapacity |
P96445
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Uris Theatre, hasLargeSeatingCapacity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargeSeatingCapacity Context triple: [Uris Theatre, hasLargeSeatingCapacity, true]
-
A.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
-
C.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
D.
hasSeatingCapacityCategory
chosen
Indicates the classification of an entity based on the range or category of how many people it can seat.
-
E.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a86be308190973fea5d7db8ba9d |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.