Triple
T36939076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Hinton |
E913700
|
entity |
| Predicate | songIsCoverOf |
P95695
|
FINISHED |
| Object | Funny How Time Slips Away |
—
|
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: Funny How Time Slips Away | Statement: [Joe Hinton, songIsCoverOf, Funny How Time Slips Away]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songIsCoverOf Context triple: [Joe Hinton, songIsCoverOf, Funny How Time Slips Away]
-
A.
hasCoverVersionPerformer
chosen
Indicates that an entity is the performer of a cover version of another entity’s original work.
-
B.
hasCoverVersionInGenre
Indicates that an entity has at least one cover version that is performed or produced within a specified musical genre.
-
C.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
D.
trackCoveredBy
Indicates that one track or path is physically overlaid, shielded, or enclosed by another structure or material.
-
E.
featuresSongwriterCovered
Indicates that one entity includes or highlights a songwriter whose work has been covered in a song or performance by another 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe174a508190a717d6e962a90fb7 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.