Triple
T20726054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirumular |
E509437
|
entity |
| Predicate | TirumantiramGenre |
P135866
|
FINISHED |
| Object | devotional poetry |
—
|
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: devotional poetry | Statement: [Tirumular, TirumantiramGenre, devotional poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TirumantiramGenre Context triple: [Tirumular, TirumantiramGenre, devotional poetry]
-
A.
religiousLiteratureType
chosen
Indicates the specific category or type of religious literature associated with an entity, such as scripture, commentary, liturgy, or devotional text.
-
B.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
C.
positionInTirumurai
Indicates the specific location or ordering of a work or hymn within the Tirumurai canon.
-
D.
mantraText
Indicates that a mantra is associated with a specific textual content or wording.
-
E.
devotionalTitleType
Indicates the specific kind or category of title used in a devotional context (such as a form of address or honorific used in religious devotion).
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e7aabc819084f9e9fd45e877fd |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:29 p.m.