Triple
T35524679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keep On Keepin' On |
E1026639
|
entity |
| Predicate | hasPrimaryMusicalElement |
P60129
|
FINISHED |
| Object | vocal harmonies |
—
|
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: vocal harmonies | Statement: [Keep On Keepin' On, hasPrimaryMusicalElement, vocal harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryMusicalElement Context triple: [Keep On Keepin' On, hasPrimaryMusicalElement, vocal harmonies]
-
A.
hasAdditionalMusicalElements
Indicates that an entity includes extra or supplementary musical components beyond its primary or standard musical elements.
-
B.
usesMusicalElement
chosen
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
E.
hasMelodyInstrument
Indicates that something uses or features a particular instrument to carry the main melody.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.