Triple
T24096042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You’ll Accomp’ny Me |
E596919
|
entity |
| Predicate | hasProminentVocalFeature |
P46281
|
FINISHED |
| Object | male lead vocals |
—
|
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: male lead vocals | Statement: [You’ll Accomp’ny Me, hasProminentVocalFeature, male lead vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentVocalFeature Context triple: [You’ll Accomp’ny Me, hasProminentVocalFeature, male lead vocals]
-
A.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
B.
hasVocalPerspective
Indicates that one entity expresses or frames content from the point of view or voice of another entity.
-
C.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
D.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
E.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd24ad9c8190ae81bcc5eae6e159 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:58 p.m.