Triple
T29907990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wave |
E759590
|
entity |
| Predicate | titleTrackMusicGenre |
P164195
|
FINISHED |
| Object | bossa nova standard |
—
|
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: bossa nova standard | Statement: [Wave, titleTrackMusicGenre, bossa nova standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleTrackMusicGenre Context triple: [Wave, titleTrackMusicGenre, bossa nova standard]
-
A.
trackName
Indicates the name or title assigned to a specific track (such as a song, audio piece, or route) in the relationship.
-
B.
musicBrainzType
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
-
C.
musicField
Indicates a relationship where an entity is associated with a particular field, genre, or domain within music.
-
D.
genreOfRecordedWork
chosen
Indicates that a recorded work (such as a song, album, or audio piece) belongs to a particular artistic or musical genre.
-
E.
hasSoundtrackGenre
Indicates that something (such as a work or production) has a soundtrack that belongs to a specified musical 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 29, 2026, 6:09 p.m.