Triple
T9831683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavadee |
E238999
|
entity |
| Predicate | devotionalText |
P36541
|
FINISHED |
| Object | Tamil hymns to Murugan |
—
|
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: Tamil hymns to Murugan | Statement: [Cavadee, devotionalText, Tamil hymns to Murugan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalText Context triple: [Cavadee, devotionalText, Tamil hymns to Murugan]
-
A.
devotionalTitle
Indicates that one entity serves as the devotional or religiously themed title associated with another entity.
-
B.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
C.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
D.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
E.
hasDevotionalFormula
chosen
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb335623c8190902de29795bce87d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.