Triple
T33609358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C4 |
E860947
|
entity |
| Predicate | showsLyricalDevelopmentOf |
P177630
|
FINISHED |
| Object | Kendrick Lamar |
—
|
NE NERFINISHED |
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: Kendrick Lamar | Statement: [C4, showsLyricalDevelopmentOf, Kendrick Lamar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsLyricalDevelopmentOf Context triple: [C4, showsLyricalDevelopmentOf, Kendrick Lamar]
-
A.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
hasLyricalLanguage
Indicates that something (such as a text or expression) employs poetic, expressive, or highly figurative language.
-
C.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
D.
hasLyricalTheme
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
E.
usesLyricalElementsFrom
Indicates that one work incorporates or borrows lyrical components (such as words, phrases, or stylistic features) from another work.
- F. None of above. chosen
Provenance (4 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_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:41 a.m.