Triple
T25337672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annakut festival |
E635318
|
entity |
| Predicate | templeActivity |
P61723
|
FINISHED |
| Object | performing special aarti ceremonies |
—
|
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: performing special aarti ceremonies | Statement: [Annakut festival, templeActivity, performing special aarti ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeActivity Context triple: [Annakut festival, templeActivity, performing special aarti ceremonies]
-
A.
templePractice
chosen
Indicates a religious or ritual activity that is performed within or in connection with a temple.
-
B.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
C.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
D.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
E.
postTemplePractice
Indicates a practice, behavior, or ritual that occurs after activities in or associated with a temple have concluded.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b39adc8190b0fc4925ce0769ed |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:32 p.m.