Triple
T15766469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridin' |
E382233
|
entity |
| Predicate | lyricHook |
P73611
|
FINISHED |
| Object | They see me rollin', they hatin' |
—
|
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: They see me rollin', they hatin' | Statement: [Ridin', lyricHook, They see me rollin', they hatin']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricHook Context triple: [Ridin', lyricHook, They see me rollin', they hatin']
-
A.
lyricFunction
Indicates the role or purpose that a set of lyrics serves within a musical work or performance.
-
B.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
C.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
D.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
-
E.
lyricType
chosen
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.