Triple
T32700602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colvin & Earle |
E836130
|
entity |
| Predicate | containsOriginalSong |
P73613
|
FINISHED |
| Object | Come What May |
—
|
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: Come What May | Statement: [Colvin & Earle, containsOriginalSong, Come What May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOriginalSong Context triple: [Colvin & Earle, containsOriginalSong, Come What May]
-
A.
containsOriginalSongs
chosen
Indicates that one entity includes or features songs that are original compositions rather than covers or adaptations.
-
B.
includesOriginalSongsBy
Indicates that one entity (such as a collection or work) contains original songs that are created or performed by another entity.
-
C.
hasOriginalMusicBy
Indicates that the original musical score or soundtrack for a work was created or composed by a specified entity.
-
D.
hasOriginalSongReleaseContext
Indicates that an original song is associated with a specific context in which it was first released (such as an event, medium, or setting).
-
E.
usesOriginalVocalsFrom
Indicates that one work incorporates the original, unaltered vocal recordings from another work.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 1, 2026, 1:10 a.m.