Triple
T35272707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champagne Poetry |
E1018711
|
entity |
| Predicate | onAppleMusic |
P182674
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Champagne Poetry, onAppleMusic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onAppleMusic Context triple: [Champagne Poetry, onAppleMusic, true]
-
A.
hasAppleMusicId
Indicates that an entity is associated with a specific identifier used by Apple Music.
-
B.
hasNotableAirplay
Indicates that something (typically a song, program, or audio content) has received a significant amount of broadcast play on radio or similar media.
-
C.
tunesFor
Indicates a relationship where one entity selects or adjusts something (such as a device, channel, or setting) specifically for the use or benefit of another entity.
-
D.
isOnSpotify
Indicates that a given entity (such as a song, album, or artist) is available or present on the Spotify platform.
-
E.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.