Triple
T3173094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahalia |
E66398
|
entity |
| Predicate | musicalAttribute |
P46763
|
FINISHED |
| Object | emotional honesty in lyrics |
—
|
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: emotional honesty in lyrics | Statement: [Mahalia, musicalAttribute, emotional honesty in lyrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalAttribute Context triple: [Mahalia, musicalAttribute, emotional honesty in lyrics]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
musicalAbility
Indicates that an entity possesses skill, talent, or proficiency in performing, creating, or understanding music.
-
C.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
D.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
E.
musicalFunction
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
- F. None of above. chosen
Provenance (4 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66facf881908b9ec687d68ce91b |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.