Triple
T23611092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opposites Attract |
E583037
|
entity |
| Predicate | lyricalLanguage |
P153271
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Opposites Attract, lyricalLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalLanguage Context triple: [Opposites Attract, lyricalLanguage, English]
-
A.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
lyricalFunction
Indicates the role or purpose that lyrics serve within a musical or poetic work, such as narrating, expressing emotion, or structuring the piece.
-
C.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
D.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
-
E.
lyricExpresses
Indicates that the content or emotion of a lyric conveys, communicates, or articulates a particular idea, feeling, or message.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f4606881908207114c5bcfe6a6 |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:45 p.m.