Triple
T32376191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lookin Ass |
E827289
|
entity |
| Predicate | recordedInGenreContext |
P164195
|
FINISHED |
| Object | contemporary 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: contemporary hip hop | Statement: [Lookin Ass, recordedInGenreContext, contemporary hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedInGenreContext Context triple: [Lookin Ass, recordedInGenreContext, contemporary hip hop]
-
A.
genreContext
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
B.
recordedGenreArtist
Indicates that an artist has recorded music in a particular genre.
-
C.
commonGenreContext
Indicates that two or more entities share a similar or related genre context, such as belonging to the same or closely related genres.
-
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.
isInGenreContext
Indicates that something occurs, is interpreted, or is relevant within the scope or framework of a particular 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 12:51 a.m.