Triple
T13851327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uchi Pillayar Temple |
E332947
|
entity |
| Predicate | openForPublicWorship |
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: [Uchi Pillayar Temple, openForPublicWorship, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openForPublicWorship Context triple: [Uchi Pillayar Temple, openForPublicWorship, true]
-
A.
openForWorship
chosen
Indicates that a place of worship is currently available and accessible for religious services or devotional activities.
-
B.
reopenedForWorship
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
-
C.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
-
D.
hasWorshipServices
Indicates that an entity conducts or provides organized religious worship services.
-
E.
allowsReligiousParticipation
Indicates that one entity grants another entity the permission or opportunity to take part in religious activities, practices, or institutions.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02d8fb788190baef7537be2baecb |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.