Triple
T8485376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aura Music |
E200819
|
entity |
| Predicate | musicStyleAssociation |
P38924
|
FINISHED |
| Object | urban Latin music |
—
|
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: urban Latin music | Statement: [Aura Music, musicStyleAssociation, urban Latin music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicStyleAssociation Context triple: [Aura Music, musicStyleAssociation, urban Latin music]
-
A.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
B.
genreAssociatedWith
chosen
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
C.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
D.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
E.
musicBrainzType
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53b359c81908174addcd6e12785 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.