Triple
T2114938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kisses Sweeter Than Wine |
E42586
|
entity |
| Predicate | originallyAdaptedFrom |
P15523
|
FINISHED |
| Object | traditional tune |
—
|
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: traditional tune | Statement: [Kisses Sweeter Than Wine, originallyAdaptedFrom, traditional tune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyAdaptedFrom Context triple: [Kisses Sweeter Than Wine, originallyAdaptedFrom, traditional tune]
-
A.
adaptedWorkOf
chosen
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
B.
adaptedAs
Indicates that one work, concept, or entity has been transformed or re-created into another form or medium based on the original.
-
C.
adaptationBy
Indicates a relationship where one entity has been modified, transformed, or reworked by another entity into a new form or version.
-
D.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
E.
notableAdaptation
Indicates that one work is a significant adaptation or reinterpretation of another work.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0724e08190a0a4210d86261d6d |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.