Triple
T18164002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophelia |
E434842
|
entity |
| Predicate | has musical feature |
P48651
|
FINISHED |
| Object | horn-driven arrangement |
—
|
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: horn-driven arrangement | Statement: [Ophelia, has musical feature, horn-driven arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has musical feature Context triple: [Ophelia, has musical feature, horn-driven arrangement]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
hasSoundtrackCharacteristic
Indicates that a soundtrack possesses a specified quality, feature, or attribute.
-
D.
hasFictionalSong
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
E.
soundtrackFeatures
Indicates that a particular soundtrack includes or showcases a given piece of music, artist, or audio element as part of its content.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec55a088190868ee0b0a310fefb |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.