Triple
T5570178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Dawg Entertainment |
E146177
|
entity |
| Predicate | hasArtistRosterFocus |
P3740
|
FINISHED |
| Object | hip hop |
—
|
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 | Statement: [Top Dawg Entertainment, hasArtistRosterFocus, hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistRosterFocus Context triple: [Top Dawg Entertainment, hasArtistRosterFocus, hip hop]
-
A.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
notableArtistRosterIncludes
Indicates that a notable artist is included as part of an entity’s recognized or distinguished roster of artists.
-
C.
hasExhibitionFocus
Indicates that an exhibition is primarily centered on, or thematically dedicated to, a particular subject, medium, or focus area.
-
D.
hasArtisticFocus
chosen
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
-
E.
hasFeaturedArtist
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0204f0d288190b9d4884665ba9116 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.