Triple
T5468040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundarar |
E122760
|
entity |
| Predicate | poeticTheme |
P61759
|
FINISHED |
| Object | devotion and grace of Shiva |
—
|
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: devotion and grace of Shiva | Statement: [Sundarar, poeticTheme, devotion and grace of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poeticTheme Context triple: [Sundarar, poeticTheme, devotion and grace of Shiva]
-
A.
languageOfPoetry
Indicates that a specified language is the language in which a given piece of poetry is written or expressed.
-
B.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
C.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
D.
literaryThemeInvolvement
chosen
Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
-
E.
poet
Indicates that an entity creates poetry or is recognized for engaging in the activity of writing poems.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.