Triple
T36070917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ooga Booga! |
E1043363
|
entity |
| Predicate | isAssociatedWithArtistStyle |
P13181
|
FINISHED |
| Object | off-kilter flows |
—
|
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: off-kilter flows | Statement: [Ooga Booga!, isAssociatedWithArtistStyle, off-kilter flows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithArtistStyle Context triple: [Ooga Booga!, isAssociatedWithArtistStyle, off-kilter flows]
-
A.
playsInStyleOf
Indicates that one entity performs, creates, or behaves in a manner characteristic of another entity’s style.
-
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.
associatedWithArtistType
Indicates that an entity has a connection or linkage to a particular category or type of artist.
-
D.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
-
E.
hasSongStyle
chosen
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.