Triple
T29332242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server Sundaram |
E743810
|
entity |
| Predicate | featuresSongPerformancesBy |
P83545
|
FINISHED |
| Object | Nagesh |
—
|
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: Nagesh | Statement: [Server Sundaram, featuresSongPerformancesBy, Nagesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSongPerformancesBy Context triple: [Server Sundaram, featuresSongPerformancesBy, Nagesh]
-
A.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
-
B.
featuresSoloPerformancesBy
chosen
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
C.
performedSongsBy
Indicates that one entity has performed songs that were created, owned, or associated with another entity.
-
D.
featuresSongFrom
Indicates that one musical work includes or incorporates a song originating from another source.
-
E.
singsSongsPerformedBy
Indicates that one entity sings songs that are performed by another entity.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: April 28, 2026, 1:30 p.m.