Triple
T25190305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildside |
E630848
|
entity |
| Predicate | usesLyricalElementsFrom |
P158417
|
FINISHED |
| Object | Walk on the Wild Side |
—
|
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: Walk on the Wild Side | Statement: [Wildside, usesLyricalElementsFrom, Walk on the Wild Side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLyricalElementsFrom Context triple: [Wildside, usesLyricalElementsFrom, Walk on the Wild Side]
-
A.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
B.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
C.
scriptUsedInLyrics
Indicates that a particular writing system or script is used to write or represent the lyrics of a song or musical work.
-
D.
hasLyricalTheme
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
E.
lyricalLanguage
Indicates that something is expressed using poetic, figurative, or highly expressive language.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0dc9908190b2d957d9c6314cfc |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 12:45 p.m.