Triple
T927197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Me Now |
E20009
|
entity |
| Predicate | chorusHook |
P1369
|
FINISHED |
| Object | "I don't know who's gonna kiss you when I'm gone" |
—
|
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: "I don't know who's gonna kiss you when I'm gone" | Statement: [Love Me Now, chorusHook, "I don't know who's gonna kiss you when I'm gone"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusHook Context triple: [Love Me Now, chorusHook, "I don't know who's gonna kiss you when I'm gone"]
-
A.
hasChorus
chosen
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
B.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
C.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
D.
chapterInvoked
Indicates that one chapter is formally brought into effect, referenced, or applied within a particular legal, procedural, or narrative context.
-
E.
chamberedFor
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.