Triple
T6269309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky Bell |
E140488
|
entity |
| Predicate | musicGroupRole |
P24740
|
FINISHED |
| Object | founding member of New Edition |
—
|
LITERAL FINISHED |
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: founding member of New Edition | Statement: [Ricky Bell, musicGroupRole, founding member of New Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicGroupRole Context triple: [Ricky Bell, musicGroupRole, founding member of New Edition]
-
A.
partnerInMusicGroupWith
Indicates that two entities are members of the same music group or band, sharing a collaborative musical partnership.
-
B.
mainPerformerMemberOf
Indicates that the primary performer in an event or work is a member of a specified group, band, ensemble, or organization.
-
C.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
D.
musicIndustryRole
Indicates the professional function or position an entity holds within the music industry ecosystem.
-
E.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063a28da081909f4bec8f7c1dedef |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.