Triple
T984661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Happy |
E21251
|
entity |
| Predicate | performedInSceneType |
P21951
|
FINISHED |
| Object | musical number |
—
|
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: musical number | Statement: [Get Happy, performedInSceneType, musical number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInSceneType Context triple: [Get Happy, performedInSceneType, musical number]
-
A.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
B.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
C.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
D.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
E.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4959fe48190a78bd811cbc888ab |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b345f890819092b51bf8128da461 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:41 p.m.