Triple
T31085545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let's Kiss and Make Up |
E792222
|
entity |
| Predicate | GershwinWork |
P170731
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Let's Kiss and Make Up, GershwinWork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GershwinWork Context triple: [Let's Kiss and Make Up, GershwinWork, yes]
-
A.
musicalWork
Indicates a relationship where an entity is identified as a musical composition or piece associated with another entity (such as a creator, performance, or recording).
-
B.
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.
-
C.
musicalTheatreWork
Indicates that one entity is a musical theatre work (such as a musical or operetta) associated with or characterized by the other entity.
-
D.
الملحن
Indicates that an entity is the composer or creator of a musical work for another entity (such as a song, piece, or performance).
-
E.
isOrchestralWorkBy
Indicates that a particular orchestral work was created or composed by a specified composer or artist.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fd30d48190a7b32d781e926691 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:02 p.m.