Triple
T24065924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm Still in Love with You |
E596086
|
entity |
| Predicate | hasSecondaryVocalStyle |
P154727
|
FINISHED |
| Object | singing |
—
|
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: singing | Statement: [I'm Still in Love with You, hasSecondaryVocalStyle, singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryVocalStyle Context triple: [I'm Still in Love with You, hasSecondaryVocalStyle, singing]
-
A.
hasHookVocalStyle
Indicates that an entity (typically a musical work or performance) features a distinctive, catchy vocal delivery or refrain intended to serve as a memorable hook.
-
B.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
introducedVocalStyleOf
Indicates that one entity initiated or brought into use the vocal style characteristic of another entity.
-
E.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5b86e88190901159a0343fe49f |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:40 p.m.