Triple
T31924162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottuswaras |
E815054
|
entity |
| Predicate | lyricContentType |
P73611
|
FINISHED |
| Object | stotras and simple praises |
—
|
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: stotras and simple praises | Statement: [Nottuswaras, lyricContentType, stotras and simple praises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricContentType Context triple: [Nottuswaras, lyricContentType, stotras and simple praises]
-
A.
lyricType
chosen
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
B.
lyricText
Indicates that one entity is the lyrical content or words of a song or musical piece associated with another entity.
-
C.
lyricExpresses
Indicates that the content or emotion of a lyric conveys, communicates, or articulates a particular idea, feeling, or message.
-
D.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
E.
lyricKeyword
Indicates that a lyric is associated with, or can be characterized by, a particular keyword or key phrase.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:03 a.m.