Triple
T15728489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Hauser |
E381278
|
entity |
| Predicate | typeOfMusicCreated |
P119956
|
FINISHED |
| Object | documentary film scores |
—
|
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: documentary film scores | Statement: [Matt Hauser, typeOfMusicCreated, documentary film scores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMusicCreated Context triple: [Matt Hauser, typeOfMusicCreated, documentary film scores]
-
A.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
B.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
C.
musicalBasisFor
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.
-
D.
songType
Indicates the specific category or genre that a given song belongs to.
-
E.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
- F. None of above. chosen
Provenance (4 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb4cc0081909efe330339474017 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.