Triple
T34365628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sure Sure |
E882001
|
entity |
| Predicate | featuresPrimaryVocalist |
P8086
|
FINISHED |
| Object | Shenseea |
E252762
|
NE 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: Shenseea | Statement: [Sure Sure, featuresPrimaryVocalist, Shenseea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPrimaryVocalist Context triple: [Sure Sure, featuresPrimaryVocalist, Shenseea]
-
A.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
B.
featuresVocalist
chosen
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
C.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
D.
primaryVocalistNationality
Indicates the nationality or country affiliation of the person who serves as the primary vocalist for a musical act or performance.
-
E.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
- F. None of above.
Provenance (4 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a031e24299c81908dcbbf1b88f43dfd |
completed | May 12, 2026, 12:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3872607284819086f49208a9338bf1 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a031ce232a48190b62bca3e94162f2f |
completed | May 12, 2026, 12:28 p.m. |
Created at: May 1, 2026, 1:58 a.m.