Triple
T14617445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karpagambal |
E343120
|
entity |
| Predicate | hasProcessionalIdol |
P59398
|
FINISHED |
| Object | Utsava murti of Karpagambal |
—
|
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: Utsava murti of Karpagambal | Statement: [Karpagambal, hasProcessionalIdol, Utsava murti of Karpagambal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessionalIdol Context triple: [Karpagambal, hasProcessionalIdol, Utsava murti of Karpagambal]
-
A.
hasIdolOf
chosen
Indicates that one entity possesses or is associated with an idol that represents, depicts, or honors another entity.
-
B.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
C.
associatedDeityProcession
Indicates that a deity is linked to, honored by, or represented in a particular procession or ceremonial parade.
-
D.
hasRitualCustodian
Indicates that one entity serves as the designated custodian or caretaker responsible for performing, preserving, or overseeing the rituals associated with another entity.
-
E.
hasIdol
Indicates that one entity admires, reveres, or looks up to another as an idol or role model.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.