Triple
T24575461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrance Cultural Arts Center |
E608090
|
entity |
| Predicate | hasTheatreSeatingType |
P55296
|
FINISHED |
| Object | proscenium theatre |
—
|
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: proscenium theatre | Statement: [Torrance Cultural Arts Center, hasTheatreSeatingType, proscenium theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheatreSeatingType Context triple: [Torrance Cultural Arts Center, hasTheatreSeatingType, proscenium theatre]
-
A.
hasSeatingClassification
Indicates that an entity is assigned a specific type or category of seating arrangement or capacity.
-
B.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
C.
hasBoxSeating
chosen
Indicates that an entity provides or includes box seating as a type of seating arrangement.
-
D.
hasBandSeating
Indicates that a venue or location provides designated seating specifically for a band or musical ensemble.
-
E.
hasSeatingInCredits
Indicates that an entity is credited for providing seating or seating-related services in the credits of a production or event.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a928896c8190af385755b1418ba6 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.