Triple
T5671114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blues |
E124977
|
entity |
| Predicate | lyricStructure |
P59491
|
FINISHED |
| Object | AAB pattern |
—
|
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: AAB pattern | Statement: [Blues, lyricStructure, AAB pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricStructure Context triple: [Blues, lyricStructure, AAB pattern]
-
A.
refrainStructure
Indicates a structural relationship where a recurring refrain section is organized, positioned, or patterned within a larger composition or sequence.
-
B.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
C.
hasLyricalForm
chosen
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
D.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
E.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.