Triple
T34239825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Shop of Horrors (Off-Broadway revival) |
E878430
|
entity |
| Predicate | isLiveEvent |
P22122
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Little Shop of Horrors (Off-Broadway revival), isLiveEvent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLiveEvent Context triple: [Little Shop of Horrors (Off-Broadway revival), isLiveEvent, yes]
-
A.
isLive
Indicates that an entity is currently broadcasting or occurring in real time, as opposed to being pre-recorded or inactive.
-
B.
isPerformedLiveBy
Indicates that an action, event, or performance occurs in real time in front of an audience and is carried out by the specified entity.
-
C.
isPublicEvent
chosen
Indicates that an event is open and accessible to the general public rather than restricted to a private or limited audience.
-
D.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
E.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.