Triple
T11684569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasi Viswanathar Temple, Kumbakonam |
E277704
|
entity |
| Predicate | openForWorship |
P100760
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kasi Viswanathar Temple, Kumbakonam, openForWorship, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openForWorship Context triple: [Kasi Viswanathar Temple, Kumbakonam, openForWorship, true]
-
A.
reopenedForWorship
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
-
B.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
C.
worshipersOffer
Indicates that worshipers present or dedicate offerings to a deity, sacred figure, or religious object.
-
D.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
worshipArea
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
- F. None of above. chosen
Provenance (4 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a463f6448190a4c8e1651a2bd905 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d8938a1f8c81908ffb049fa5fee5a7 |
completed | April 10, 2026, 6:07 a.m. |
Created at: April 8, 2026, 9:40 p.m.