Triple
T28378725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonesome Lover |
E718829
|
entity |
| Predicate | performerOnNotableRecording |
P153264
|
FINISHED |
| Object | Max Roach |
—
|
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: Max Roach | Statement: [Lonesome Lover, performerOnNotableRecording, Max Roach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerOnNotableRecording Context triple: [Lonesome Lover, performerOnNotableRecording, Max Roach]
-
A.
performerNotableWork
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
B.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
C.
artistRecorded
chosen
Indicates that an artist has recorded a particular musical work, track, or album.
-
D.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
E.
notableRecordingType
Indicates that the subject is notably associated with recordings of a particular type or format.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:05 a.m.