Triple
T31864665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eighties |
E813417
|
entity |
| Predicate | influencedSong |
P28252
|
FINISHED |
| Object | Come as You Are |
—
|
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: Come as You Are | Statement: [Eighties, influencedSong, Come as You Are]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedSong Context triple: [Eighties, influencedSong, Come as You Are]
-
A.
inspiredSong
chosen
Indicates that one entity (such as an event, person, or work) served as the creative inspiration or motivating influence for the creation of a particular song.
-
B.
influencedArtist
Indicates that one artist has had a significant impact on the style, work, or development of another artist.
-
C.
influencesMusicOf
Indicates that one entity has an effect on, shapes, or contributes to the musical style, content, or development of another entity.
-
D.
influencedInstrument
Indicates that one entity has affected, shaped, or altered a musical instrument or tool in some way, such as its design, use, style, or development.
-
E.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 30, 2026, 11:53 p.m.