Triple
T30739459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yummy Yummy |
E782652
|
entity |
| Predicate | hasOriginalMemberPerformer |
P153591
|
FINISHED |
| Object | Murray Cook |
—
|
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: Murray Cook | Statement: [Yummy Yummy, hasOriginalMemberPerformer, Murray Cook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalMemberPerformer Context triple: [Yummy Yummy, hasOriginalMemberPerformer, Murray Cook]
-
A.
originalPerformer
Indicates that an entity is the first or initial performer of a work, role, or performance.
-
B.
hasOriginalReleaseArtist
Indicates that an entity (such as a work or recording) is associated with the artist who first released it.
-
C.
mainPerformerMemberOf
Indicates that the primary performer in an event or work is a member of a specified group, band, ensemble, or organization.
-
D.
hasNotablePerformerMembership
Indicates that an entity is or has been a distinguished or noteworthy member of a particular performer group, organization, or ensemble.
-
E.
originalBandMember
chosen
Indicates that a person was part of the band’s lineup at the time the band was first formed.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 8:37 p.m.