Triple
T7592697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neither One of Us (Wants to Be the First to Say Goodbye) |
E179776
|
entity |
| Predicate | isVocalMusic |
P25705
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Neither One of Us (Wants to Be the First to Say Goodbye), isVocalMusic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVocalMusic Context triple: [Neither One of Us (Wants to Be the First to Say Goodbye), isVocalMusic, true]
-
A.
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.
-
B.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
E.
isVocalShowcaseFor
Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal abilities.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b92c348190b547f0aacfb8d6be |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.