Triple
T17187128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood and Time |
E417137
|
entity |
| Predicate | musicalStyleComparedTo |
P86170
|
FINISHED |
| Object | Neurosis side projects |
—
|
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: Neurosis side projects | Statement: [Blood and Time, musicalStyleComparedTo, Neurosis side projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalStyleComparedTo Context triple: [Blood and Time, musicalStyleComparedTo, Neurosis side projects]
-
A.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
B.
hasMusicalStyleSimilarTo
chosen
Indicates that two entities share a comparable or closely related musical style or sound.
-
C.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
D.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
genreContrast
Indicates a relationship where two or more works are compared or juxtaposed based on differences between their genres.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d96fc588190ad2177d8bb346373 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.