Triple
T3743864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Edinburgh Military Tattoo |
E79763
|
entity |
| Predicate | soundtrack |
P49119
|
FINISHED |
| Object | live music |
—
|
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: live music | Statement: [Royal Edinburgh Military Tattoo, soundtrack, live music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundtrack Context triple: [Royal Edinburgh Military Tattoo, soundtrack, live music]
-
A.
soundtrackType
Indicates the specific category or format of a soundtrack associated with a work, such as score, compilation, or original soundtrack.
-
B.
isSoundtrackOf
chosen
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.
-
C.
filmMusicBy
Indicates that a film’s musical score or soundtrack was composed or created by a particular person or group.
-
D.
soundtrackTitle
Indicates the title assigned to a soundtrack associated with a work or production.
-
E.
filmSoundtrackFor
Indicates that a particular soundtrack is created for, associated with, or used as the official musical accompaniment to a specific film.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb576b5881908515d64c71f11a16 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.