Triple
T13882535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sha Na Na |
E333752
|
entity |
| Predicate | performanceTheme |
P25955
|
FINISHED |
| Object | 1950s nostalgia |
—
|
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: 1950s nostalgia | Statement: [Sha Na Na, performanceTheme, 1950s nostalgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceTheme Context triple: [Sha Na Na, performanceTheme, 1950s nostalgia]
-
A.
performanceStyle
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
B.
performedThemeFor
Indicates that an agent carried out or executed a performance specifically for a particular theme or subject.
-
C.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
performanceFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to its performance or operational effectiveness.
-
E.
performanceTuningBy
Indicates that an entity’s performance has been adjusted, optimized, or fine-tuned by another 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.