Triple
T23249235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartoon Records |
E581685
|
entity |
| Predicate | releasedRecordingsBy |
P51851
|
FINISHED |
| Object | Tom Tom Club |
—
|
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: Tom Tom Club | Statement: [Cartoon Records, releasedRecordingsBy, Tom Tom Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedRecordingsBy Context triple: [Cartoon Records, releasedRecordingsBy, Tom Tom Club]
-
A.
releasedMusicBy
chosen
Indicates that a musical work (such as a song, album, or EP) was issued or made publicly available by a particular artist or musical act.
-
B.
hasDiscographyWith
Indicates a relationship where two or more musical entities are associated through a shared or jointly produced discography.
-
C.
hasDiscographyIn
Indicates that an entity has released or contributed to musical recordings within a particular region, market, or catalog context.
-
D.
hasTributeReleasesFor
Indicates that one entity has released or produced tribute works (such as albums, songs, or performances) dedicated to another entity.
-
E.
recordingsFrom
Indicates a relationship where one entity serves as the source or origin of recordings that are associated with or derived from it.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f4d7e4819085eec6279696db34 |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.