Triple
T31227310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoo-Be-Doo-Be-Doo-Da-Day |
E796174
|
entity |
| Predicate | musicalArtistLabel |
P61234
|
FINISHED |
| Object | Stevie Wonder |
—
|
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: Stevie Wonder | Statement: [Shoo-Be-Doo-Be-Doo-Da-Day, musicalArtistLabel, Stevie Wonder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalArtistLabel Context triple: [Shoo-Be-Doo-Be-Doo-Da-Day, musicalArtistLabel, Stevie Wonder]
-
A.
recordLabelArtist
Indicates that a musical artist is signed to, represented by, or releases recordings through a particular record label.
-
B.
musicLabelType
Indicates the specific category or classification of a music label, such as its role, scope, or organizational type.
-
C.
musicalArtistAssociated
Indicates a relationship where one musical artist is professionally connected or affiliated with another, such as through collaboration, membership, or frequent association.
-
D.
musicalArtistName
chosen
Indicates that the predicate specifies the name of a musical artist associated with an entity.
-
E.
musicalArtistMember
Indicates that one entity is a musical artist who is or was a member of another musical group or act.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 9:10 p.m.