Triple
T9597395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Theater Oakland |
E231565
|
entity |
| Predicate | reopenedAsLiveVenue |
P55982
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Fox Theater Oakland, reopenedAsLiveVenue, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsLiveVenue Context triple: [Fox Theater Oakland, reopenedAsLiveVenue, 2009]
-
A.
reopenedAsConcertHall
chosen
Indicates that a previously closed or differently purposed venue has been opened again specifically to function as a concert hall.
-
B.
mainVenueOpened
Indicates that the primary venue associated with an event or organization has begun operations or officially opened.
-
C.
venueRebuilt
Indicates that a venue has been reconstructed or significantly renovated after a prior state of damage, disuse, or demolition.
-
D.
closedVenue
Indicates that a venue is not open or available for use during a given time or event.
-
E.
homeVenueOpened
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a34f5408190ba72ba8311eb259c |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.