Triple
T31965872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Shook Up (Broadway musical) |
E816172
|
entity |
| Predicate | previewPerformancesBegan |
P197395
|
FINISHED |
| Object | 2005-02-20 |
—
|
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: 2005-02-20 | Statement: [All Shook Up (Broadway musical), previewPerformancesBegan, 2005-02-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previewPerformancesBegan Context triple: [All Shook Up (Broadway musical), previewPerformancesBegan, 2005-02-20]
-
A.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
B.
presentsPerformancesBy
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
-
C.
performances
Indicates that an entity stages, presents, or executes artistic or entertainment events for an audience.
-
D.
totalPerformances
Indicates the total number of times a particular performance, show, or act has been carried out.
-
E.
laterPerformedOnStageWithinShow
Indicates that one performance or act occurred later on stage within the same show than another performance or act.
- F. None of above. chosen
Provenance (4 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: May 1, 2026, 12:09 a.m.