Triple
T32738021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beans and Cornbread |
E837144
|
entity |
| Predicate | hasLyricalStructure |
P59491
|
FINISHED |
| Object | call-and-response |
—
|
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 | Statement: [Beans and Cornbread, hasLyricalStructure, call-and-response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricalStructure Context triple: [Beans and Cornbread, hasLyricalStructure, call-and-response]
-
A.
hasLyricalForm
chosen
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
B.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
C.
hasLyricalLanguage
Indicates that something (such as a text or expression) employs poetic, expressive, or highly figurative language.
-
D.
hasLyricalTheme
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
E.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:12 a.m.