Triple
T29284014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valse Triste |
E742458
|
entity |
| Predicate | usesExistingMusic |
P149801
|
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: [Valse Triste, usesExistingMusic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExistingMusic Context triple: [Valse Triste, usesExistingMusic, true]
-
A.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
-
B.
musicUsed
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
-
C.
usesTuneOf
chosen
Indicates that one work is created to be performed with, or is based on, the melody or musical setting originally belonging to another work.
-
D.
usesInstrumentalsFrom
Indicates that one entity incorporates or makes use of the instrumental tracks or instrumental components created or provided by another entity.
-
E.
hasDifferentMusicFrom
Indicates that two entities have music that is not the same in style, content, or identity.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 12:56 p.m.