Triple
T4762648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavani |
E105731
|
entity |
| Predicate | ShringarLavaniFocus |
P25938
|
FINISHED |
| Object | romantic and erotic themes |
—
|
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: romantic and erotic themes | Statement: [Lavani, ShringarLavaniFocus, romantic and erotic themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ShringarLavaniFocus Context triple: [Lavani, ShringarLavaniFocus, romantic and erotic themes]
-
A.
isPancharangaKshetram
Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
-
B.
lyricFocus
chosen
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
C.
isDivyaDesam
Indicates that a location is one of the 108 sacred Vishnu temples (Divya Desams) revered in the Tamil Vaishnavite tradition.
-
D.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
E.
languageOfChant
Indicates the language in which a chant is performed or expressed.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.