Triple
T1441537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If This Isn’t Love |
E31082
|
entity |
| Predicate | vocalPerformance |
P25705
|
FINISHED |
| Object | powerful 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: powerful vocals | Statement: [If This Isn’t Love, vocalPerformance, powerful vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformance Context triple: [If This Isn’t Love, vocalPerformance, powerful vocals]
-
A.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
-
B.
hasVocals
chosen
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
C.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
D.
performedSong
Indicates that an entity (such as an artist or performer) has given a performance of a particular song.
-
E.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.