Triple
T30079980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If U Seek Amy |
E764426
|
entity |
| Predicate | radioEditLyricChange |
P14953
|
FINISHED |
| Object | If you seek Amy → If you see Amy |
—
|
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: If you seek Amy → If you see Amy | Statement: [If U Seek Amy, radioEditLyricChange, If you seek Amy → If you see Amy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioEditLyricChange Context triple: [If U Seek Amy, radioEditLyricChange, If you seek Amy → If you see Amy]
-
A.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another entity.
-
B.
modifiedLyricsDetail
chosen
Indicates that the relationship specifies detailed information about how the original lyrics have been altered or modified.
-
C.
lyricText
Indicates that one entity is the lyrical content or words of a song or musical piece associated with another entity.
-
D.
lyricAdaptationBy
Indicates that the lyrics of a work have been adapted, modified, or reinterpreted by a specified agent or creator.
-
E.
lyricFunction
Indicates the role or purpose that a set of lyrics serves within a musical work or performance.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d4086c08190ac65ff5d29fa06dc |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:02 p.m.