Triple
T27933626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exclusive |
E708047
|
entity |
| Predicate | notableWorkIncludesSong |
P88822
|
FINISHED |
| Object | Kiss Kiss |
—
|
NE NERFINISHED |
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: Kiss Kiss | Statement: [Exclusive, notableWorkIncludesSong, Kiss Kiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkIncludesSong Context triple: [Exclusive, notableWorkIncludesSong, Kiss Kiss]
-
A.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
B.
notableSongsIncluded
chosen
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
-
C.
notableSongContributions
Indicates that an entity has made significant creative or performance contributions to one or more songs.
-
D.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
E.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: April 27, 2026, 7:04 p.m.