Triple
T36971149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Music |
E914571
|
entity |
| Predicate | hasTrackWithSpokenWord |
P108014
|
FINISHED |
| Object | Malcolm, Malcolm – Semper Malcolm |
—
|
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: Malcolm, Malcolm – Semper Malcolm | Statement: [Fire Music, hasTrackWithSpokenWord, Malcolm, Malcolm – Semper Malcolm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackWithSpokenWord Context triple: [Fire Music, hasTrackWithSpokenWord, Malcolm, Malcolm – Semper Malcolm]
-
A.
hasSpokenSampleBy
Indicates that an entity has a spoken or audio sample that was produced or performed by a specified agent.
-
B.
hasSpokenWordSections
chosen
Indicates that something contains or includes sections where words are spoken rather than sung or played.
-
C.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
D.
hasTrackWith
Indicates that something includes, contains, or is associated with a specific track (such as a path, course, or recorded item).
-
E.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 3, 2026, 4:14 p.m.