Triple
T33685195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Didn't It Rain" |
E863005
|
entity |
| Predicate | performanceStyleFeature |
P13362
|
FINISHED |
| Object | call-and-response vocals |
—
|
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: call-and-response vocals | Statement: ["Didn't It Rain", performanceStyleFeature, call-and-response vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceStyleFeature Context triple: ["Didn't It Rain", performanceStyleFeature, call-and-response vocals]
-
A.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
B.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
C.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
-
D.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
E.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:43 a.m.