Triple
T33202069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urvasi Urvasi |
E849926
|
entity |
| Predicate | hasPlaybackSinger |
P158310
|
FINISHED |
| Object | S. P. Balasubrahmanyam |
—
|
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: S. P. Balasubrahmanyam | Statement: [Urvasi Urvasi, hasPlaybackSinger, S. P. Balasubrahmanyam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaybackSinger Context triple: [Urvasi Urvasi, hasPlaybackSinger, S. P. Balasubrahmanyam]
-
A.
isSungBy
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
B.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
leadPlaybackSinger
chosen
Indicates that one entity serves as the primary or main playback singer for another entity, such as a song or performance.
-
D.
hasHookSinger
Indicates that one entity serves as the hook singer (performing the main recurring vocal refrain) for another entity, typically a song or musical track.
-
E.
hasBackingMusician
Indicates that one entity serves as a supporting or accompanying musician for another entity, typically in a performance or recording 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:30 a.m.