Triple
T32511407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Palace (Bakersfield nightclub) |
E830939
|
entity |
| Predicate | hasLiveMusicSchedule |
P130151
|
FINISHED |
| Object | regular |
—
|
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: regular | Statement: [Crystal Palace (Bakersfield nightclub), hasLiveMusicSchedule, regular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveMusicSchedule Context triple: [Crystal Palace (Bakersfield nightclub), hasLiveMusicSchedule, regular]
-
A.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
D.
hasMusicProgram
Indicates that an entity offers or is associated with an organized music-related program or curriculum.
-
E.
hasLivePerformanceStatus
chosen
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 1 a.m.