Triple
T984671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Happy |
E21251
|
entity |
| Predicate | backingInSummerStockPerformance |
P21954
|
FINISHED |
| Object | male chorus |
—
|
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: male chorus | Statement: [Get Happy, backingInSummerStockPerformance, male chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backingInSummerStockPerformance Context triple: [Get Happy, backingInSummerStockPerformance, male chorus]
-
A.
summerBase
Indicates a base or location where an entity is situated or operates specifically during the summer season.
-
B.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
C.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
-
D.
summerFeature
Indicates that something is a characteristic, attraction, or condition specifically associated with or prominent during the summer season.
-
E.
previousSummerOlympics
Indicates that one Olympic Games event occurred immediately before another in the chronological sequence of Summer Olympic Games.
- 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.