Triple
T20387363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spike Spiegel |
E497992
|
entity |
| Predicate | musicalStyleAssociation |
P33180
|
FINISHED |
| Object | jazz |
—
|
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: jazz | Statement: [Spike Spiegel, musicalStyleAssociation, jazz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalStyleAssociation Context triple: [Spike Spiegel, musicalStyleAssociation, jazz]
-
A.
musicalAssociation
Indicates a relationship where entities are connected through music, such as collaboration, influence, shared performance, or other musically relevant association.
-
B.
musicalArtistAssociated
Indicates a relationship where one musical artist is professionally connected or affiliated with another, such as through collaboration, membership, or frequent association.
-
C.
genreAssociatedWith
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
D.
styleOfMusic
chosen
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
E.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790c935881908f901d058e6a83a9 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:28 a.m.