Triple
T30806159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Guns II |
E784503
|
entity |
| Predicate | soundtrackAlbumTitle |
P45357
|
FINISHED |
| Object | Blaze of Glory |
—
|
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: Blaze of Glory | Statement: [Young Guns II, soundtrackAlbumTitle, Blaze of Glory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundtrackAlbumTitle Context triple: [Young Guns II, soundtrackAlbumTitle, Blaze of Glory]
-
A.
soundtrackTitle
chosen
Indicates the title assigned to a soundtrack associated with a work or production.
-
B.
soundtrackRelease
Indicates that a soundtrack has been officially released, typically as a published audio recording associated with another work.
-
C.
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.
-
D.
soundtrackType
Indicates the specific category or format of a soundtrack associated with a work, such as score, compilation, or original soundtrack.
-
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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:43 p.m.