Triple
T20056395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia (Ludacris song) |
E499346
|
entity |
| Predicate | hasSoulfulHook |
P68739
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Georgia (Ludacris song), hasSoulfulHook, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoulfulHook Context triple: [Georgia (Ludacris song), hasSoulfulHook, true]
-
A.
hasMelodicHook
Indicates that a musical piece contains a distinctive, memorable melodic phrase designed to catch the listener’s attention.
-
B.
hasChorusHook
Indicates that a musical work features a prominent, recurring chorus section that serves as a memorable hook.
-
C.
hasSoulfulProduction
chosen
Indicates that something (typically a piece of music) features production characterized by emotional depth, warmth, and stylistic elements associated with soul music.
-
D.
hasHookSinger
Indicates that one entity serves as the hook singer (performing the main recurring vocal refrain) for another entity, typically a song or musical track.
-
E.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663337d0c8190b82422802396cd67 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.