Triple
T33609766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahki |
E860956
|
entity |
| Predicate | notableGenreRole |
P32515
|
FINISHED |
| Object | American hip hop producer |
—
|
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: American hip hop producer | Statement: [Rahki, notableGenreRole, American hip hop producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenreRole Context triple: [Rahki, notableGenreRole, American hip hop producer]
-
A.
notableGenreAsFilmmaker
Indicates the film genre for which a filmmaker is particularly recognized or distinguished.
-
B.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
C.
notableGenreOfFilm
Indicates that a particular genre is especially characteristic, prominent, or noteworthy for a given film.
-
D.
notableRoleInRepertoire
Indicates that an entity holds a particularly significant or defining role within another entity’s body of work or performances.
-
E.
genreRole
chosen
Indicates a relationship where an entity holds a specific functional or categorical role within 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.