Triple
T33755024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beautiful Liar (Spanish Version) |
E864952
|
entity |
| Predicate | hasAdaptedLyrics |
P110957
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Beautiful Liar (Spanish Version), hasAdaptedLyrics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptedLyrics Context triple: [Beautiful Liar (Spanish Version), hasAdaptedLyrics, yes]
-
A.
lyricAdaptationBy
Indicates that the lyrics of a work have been adapted, modified, or reinterpreted by a specified agent or creator.
-
B.
lyricsAdaptedFrom
chosen
Indicates that the lyrics of one work are derived, adapted, or modified from the lyrics of another pre-existing work.
-
C.
hasVariableLyrics
Indicates that the lyrics of a song or musical piece change between different performances, versions, or contexts.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
hasAdditionalLyricsBy
Indicates that an entity (such as a musical work or track) includes extra or modified lyrics contributed by a specified person or group beyond the original lyricist.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:45 a.m.