Triple
T15354131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watch Your Mouth |
E367129
|
entity |
| Predicate | musicGenreScene |
P56238
|
FINISHED |
| Object | UK urban music scene |
—
|
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: UK urban music scene | Statement: [Watch Your Mouth, musicGenreScene, UK urban music scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicGenreScene Context triple: [Watch Your Mouth, musicGenreScene, UK urban music scene]
-
A.
musicGenreRegion
Indicates the association between a music genre and the geographic region where it originates, is most prevalent, or is culturally significant.
-
B.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
C.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
-
D.
associatedWithMusicScene
chosen
Indicates a relationship where an entity is connected or linked to a particular music scene, culture, or community.
-
E.
musicMovement
Indicates a relationship where a musical work, performance, or composition is associated with a specific movement or section within a larger musical piece.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2a8e88819093e4b7479b2c80cd |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.