Triple
T31049669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | These Are My Songs |
E791223
|
entity |
| Predicate | primarySongwriterOfTitleTrack |
P123166
|
FINISHED |
| Object | Charlie Chaplin |
E4112
|
NE 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: Charlie Chaplin | Statement: [These Are My Songs, primarySongwriterOfTitleTrack, Charlie Chaplin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySongwriterOfTitleTrack Context triple: [These Are My Songs, primarySongwriterOfTitleTrack, Charlie Chaplin]
-
A.
songWrittenBy
Indicates that a particular song was created or composed by a specific person or group.
-
B.
keySongwriter
chosen
Indicates that the subject is the primary or main songwriter responsible for creating the song associated with the object.
-
C.
songwritingCredit
Indicates that one entity is credited as a songwriter or co-songwriter for a musical work associated with another entity.
-
D.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
E.
titleSongComposer
Indicates that one entity is the composer of the title song associated with another entity (such as a film, show, or album).
- F. None of above.
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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29389f64a4819094b146faa96ed164 |
completed | June 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9 p.m.