Triple
T29510129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zildjian Cymbals |
E748624
|
entity |
| Predicate | servesMusiciansInGenre |
P131541
|
FINISHED |
| Object | 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: rock | Statement: [Zildjian Cymbals, servesMusiciansInGenre, rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMusiciansInGenre Context triple: [Zildjian Cymbals, servesMusiciansInGenre, rock]
-
A.
servedGenre
chosen
Indicates that a service, venue, or provider offers or specializes in a particular genre (such as a style, category, or type of content).
-
B.
musicPatrons
Indicates a relationship where one entity financially supports, sponsors, or otherwise acts as a patron for another entity’s musical activities, works, or performances.
-
C.
musicOftenPerformedBy
Indicates that a particular piece of music, genre, or work is frequently performed or interpreted by a specific performer or group.
-
D.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
E.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 28, 2026, 4:31 p.m.