Triple
T23964381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natty Dread Taking Over |
E604019
|
entity |
| Predicate | hasMusicalGroupMember |
P22076
|
FINISHED |
| Object | Culture |
—
|
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: Culture | Statement: [Natty Dread Taking Over, hasMusicalGroupMember, Culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalGroupMember Context triple: [Natty Dread Taking Over, hasMusicalGroupMember, Culture]
-
A.
hasBandMember
chosen
Indicates that a musical group includes a specific individual as one of its members.
-
B.
musicalArtistMember
Indicates that one entity is a musical artist who is or was a member of another musical group or act.
-
C.
recordingArtistMemberOf
Indicates that a recording artist is a member of, or affiliated with, a particular musical group, band, or ensemble.
-
D.
associatedBandOfMembers
Indicates a relationship where a specific band is linked to the individual members who belong to or perform in that band.
-
E.
partnerInMusicGroupWith
Indicates that two entities are members of the same music group or band, sharing a collaborative musical partnership.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d616dc8190accd8f343a809e6f |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:24 p.m.