Triple
T32641422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electric Dragon 80.000 V |
E834487
|
entity |
| Predicate | featuresSoundtrackBy |
P31734
|
FINISHED |
| Object | Mach 1.67 |
—
|
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: Mach 1.67 | Statement: [Electric Dragon 80.000 V, featuresSoundtrackBy, Mach 1.67]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSoundtrackBy Context triple: [Electric Dragon 80.000 V, featuresSoundtrackBy, Mach 1.67]
-
A.
soundtrackFeatures
Indicates that a particular soundtrack includes or showcases a given piece of music, artist, or audio element as part of its content.
-
B.
sangSoundtrackFor
chosen
Indicates that one entity performed or recorded the soundtrack music for a work associated with another entity.
-
C.
filmMusicFunction
Indicates the functional role that a piece of music serves within a film, such as underscoring action, defining mood, or supporting narrative elements.
-
D.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
-
E.
partOfSoundtrackForGenre
Indicates that a piece of music or audio is included in the soundtrack associated with a particular genre.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a011e5a419081908d06a07b395ebd97 |
completed | May 11, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_6a011de119048190b27d361cffabc228 |
completed | May 11, 2026, 12:08 a.m. |
Created at: May 1, 2026, 1:07 a.m.