Triple
T7830467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relight My Fire |
E181351
|
entity |
| Predicate | hasChorusHook |
P79253
|
FINISHED |
| Object | "Relight my fire, your love is my only desire" |
—
|
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: "Relight my fire, your love is my only desire" | Statement: [Relight My Fire, hasChorusHook, "Relight my fire, your love is my only desire"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusHook Context triple: [Relight My Fire, hasChorusHook, "Relight my fire, your love is my only desire"]
-
A.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
B.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
C.
hasChorusStyle
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
-
D.
hasChorusSample
Indicates that one musical work incorporates a sampled portion of the chorus from another work.
-
E.
hasChorusDescription
Indicates that an entity has a textual description specifically about its chorus section.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04ac013c81909533fa348776f50c |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:44 p.m.