Triple
T34364413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcohol-Free |
E881967
|
entity |
| Predicate | containsLyricsAbout |
P7609
|
FINISHED |
| Object | romantic intoxication without alcohol |
—
|
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: romantic intoxication without alcohol | Statement: [Alcohol-Free, containsLyricsAbout, romantic intoxication without alcohol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLyricsAbout Context triple: [Alcohol-Free, containsLyricsAbout, romantic intoxication without alcohol]
-
A.
hasLyricsMentioning
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
hasLyricsTheme
chosen
Indicates that the lyrics of a work primarily concern or revolve around a specified theme or subject.
-
E.
lyricKeyword
Indicates that a lyric is associated with, or can be characterized by, a particular keyword or key phrase.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:58 a.m.