Triple
T24126164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electric Circus |
E597805
|
entity |
| Predicate | musicGenrePresented |
P33180
|
FINISHED |
| Object | psychedelic rock |
—
|
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: psychedelic rock | Statement: [Electric Circus, musicGenrePresented, psychedelic rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicGenrePresented Context triple: [Electric Circus, musicGenrePresented, psychedelic rock]
-
A.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
B.
musicForGenre
Indicates that something (such as a piece, track, or work) is intended to be used as or associated with music belonging to a particular genre.
-
C.
styleOfMusic
chosen
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
D.
musicGenrePreferred
Indicates that an entity has a liking for or favors a particular music genre over others.
-
E.
musicGenreBroad
Indicates that one music genre is a broader, more general category that encompasses another, more specific music genre.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee9086481909710c6d3291242c3 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.