Triple
T18737826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Padmavathi Ammavari Temple |
E458209
|
entity |
| Predicate | hasDailyRituals |
P4193
|
FINISHED |
| Object | archana |
—
|
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: archana | Statement: [Sri Padmavathi Ammavari Temple, hasDailyRituals, archana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDailyRituals Context triple: [Sri Padmavathi Ammavari Temple, hasDailyRituals, archana]
-
A.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
B.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
D.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768b80ac8190bc05628d64f86fc9 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.