Triple
T13500953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The War of the Roses (1989 film score) |
E320887
|
entity |
| Predicate | isAudioWork |
P84944
|
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: [The War of the Roses (1989 film score), isAudioWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAudioWork Context triple: [The War of the Roses (1989 film score), isAudioWork, true]
-
A.
isAudioWorkForVisualWork
Indicates that one work serves as the audio component or soundtrack specifically created for or associated with a particular visual work.
-
B.
isMusicalWork
chosen
Indicates that one entity is a musical composition or piece created as an artistic work.
-
C.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
D.
isWorkSong
Indicates that the subject is a song specifically created for or associated with a particular work, job, or labor activity.
-
E.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf50f4a48190a44fc537b78c32fd |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.