Triple
T25749012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost of Soulja Slim |
E648418
|
entity |
| Predicate | homageStyle |
P121907
|
FINISHED |
| Object | lyrical tribute |
—
|
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: lyrical tribute | Statement: [Ghost of Soulja Slim, homageStyle, lyrical tribute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homageStyle Context triple: [Ghost of Soulja Slim, homageStyle, lyrical tribute]
-
A.
honorStyle
Indicates the manner or level of respect, formality, or honor expressed toward or between entities.
-
B.
honourStyle
Indicates a relationship where one entity follows, respects, or upholds the manner, customs, or stylistic approach associated with another.
-
C.
paysHomageTo
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
-
D.
heritageStyle
Indicates that one entity is characterized by, designed in, or associated with a particular heritage or traditional style defined by the other entity.
-
E.
inTheStyleOf
chosen
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7d0d988190bf868b15d37daa28 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:32 a.m.