Triple
T28666356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blade Runner 2049 score |
E725595
|
entity |
| Predicate | basedOnMusicalStyleOf |
P94602
|
FINISHED |
| Object | Vangelis |
—
|
NE NERFINISHED |
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: Vangelis | Statement: [Blade Runner 2049 score, basedOnMusicalStyleOf, Vangelis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnMusicalStyleOf Context triple: [Blade Runner 2049 score, basedOnMusicalStyleOf, Vangelis]
-
A.
musicalBasisFor
chosen
Indicates that one musical work, idea, or element serves as the foundational source or inspiration upon which another musical work, idea, or element is built or derived.
-
B.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
C.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
D.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
-
E.
playsInStyleOf
Indicates that one entity performs, creates, or behaves in a manner characteristic of another entity’s style.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 28, 2026, 5:01 a.m.