Triple
T32607030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roulette |
E833547
|
entity |
| Predicate | hasMusicBrainzWorkID |
P36778
|
FINISHED |
| Object | b0a4a3a0-0f0b-4a0a-9a4b-0b0f0a3a0b0c |
—
|
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: b0a4a3a0-0f0b-4a0a-9a4b-0b0f0a3a0b0c | Statement: [Roulette, hasMusicBrainzWorkID, b0a4a3a0-0f0b-4a0a-9a4b-0b0f0a3a0b0c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicBrainzWorkID Context triple: [Roulette, hasMusicBrainzWorkID, b0a4a3a0-0f0b-4a0a-9a4b-0b0f0a3a0b0c]
-
A.
musicBrainzID
chosen
Indicates that an entity is associated with a specific identifier in the MusicBrainz database that uniquely references it.
-
B.
discogsID
Indicates that an entity is associated with a specific identifier used by the Discogs music database to reference it uniquely.
-
C.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
D.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
-
E.
hasWorkNumberInBachGesellschaft
Indicates that an entity is assigned a specific work number in the Bach-Gesellschaft (BG) catalog of Bach’s compositions.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 1:05 a.m.