Triple
T31924140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottuswaras |
E815054
|
entity |
| Predicate | lyricLanguageCharacteristic |
P11404
|
FINISHED |
| Object | simple Sanskrit diction |
—
|
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: simple Sanskrit diction | Statement: [Nottuswaras, lyricLanguageCharacteristic, simple Sanskrit diction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricLanguageCharacteristic Context triple: [Nottuswaras, lyricLanguageCharacteristic, simple Sanskrit diction]
-
A.
lyricCharacterization
Indicates how the lyrics portray, describe, or characterize a subject within a song or musical work.
-
B.
lyricalLanguage
Indicates that something is expressed using poetic, figurative, or highly expressive language.
-
C.
lyricsLanguage
chosen
Indicates the language in which the lyrics of a song or musical work are written or performed.
-
D.
lyricExpresses
Indicates that the content or emotion of a lyric conveys, communicates, or articulates a particular idea, feeling, or message.
-
E.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
- 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_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:03 a.m.