Triple
T32762219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Better Ask Somebody |
E837786
|
entity |
| Predicate | hasMusicalSubculture |
P142344
|
FINISHED |
| Object | hip hop culture |
—
|
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: hip hop culture | Statement: [You Better Ask Somebody, hasMusicalSubculture, hip hop culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalSubculture Context triple: [You Better Ask Somebody, hasMusicalSubculture, hip hop culture]
-
A.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
hasMusicalEnsembleGenre
Indicates that a musical ensemble is associated with or performs in a particular musical genre.
-
C.
hasMusicCategory
Indicates that something is associated with, classified under, or belongs to a particular category or type of music.
-
D.
basedOnSubculture
chosen
Indicates that something is derived from, influenced by, or rooted in a particular subculture.
-
E.
hasMusicSpecialism
Indicates that an entity has a particular area of specialization or focus within the field of music.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:13 a.m.