Triple
T8564753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palani Murugan Temple |
E202775
|
entity |
| Predicate | hasPrasadam |
P73576
|
FINISHED |
| Object | Panchamirtham |
—
|
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: Panchamirtham | Statement: [Palani Murugan Temple, hasPrasadam, Panchamirtham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrasadam Context triple: [Palani Murugan Temple, hasPrasadam, Panchamirtham]
-
A.
hasMainPrasad
chosen
Indicates that an entity is associated with or provides the primary sacred offering (main prasad) in a religious or ceremonial context.
-
B.
hasStapleFood
Indicates that an entity’s primary or regularly consumed basic food item is another specified entity.
-
C.
hasGhat
Indicates that a place or location possesses or is associated with a ghat (a series of steps or landing area leading to a body of water).
-
D.
hasMandapa
Indicates that a structure (typically a temple) includes or is associated with a mandapa, an attached or nearby pillared hall or pavilion used for rituals or gatherings.
-
E.
hasObligationOfFestiveMeal
Indicates that an entity is required to participate in or provide a festive meal as a formal obligation.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d11274819099cc33a21a993a1f |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.