Triple
T3648153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammy Award for Best Rap Performance |
E77351
|
entity |
| Predicate | notableGenreElement |
P28041
|
FINISHED |
| Object | rapping |
—
|
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: rapping | Statement: [Grammy Award for Best Rap Performance, notableGenreElement, rapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenreElement Context triple: [Grammy Award for Best Rap Performance, notableGenreElement, rapping]
-
A.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
B.
hasNotableGenre
chosen
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
C.
notableProductionType
Indicates that the subject is particularly known for producing or creating instances of the specified type.
-
D.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
E.
genreOfAppearance
Indicates the genre or type of creative work in which an entity appears.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38c22548190a271a69fb832a5a8 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.