Triple
T10615556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakrapani Temple |
E276108
|
entity |
| Predicate | languageOfLocalWorship |
P3115
|
FINISHED |
| Object | Tamil |
—
|
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: Tamil | Statement: [Chakrapani Temple, languageOfLocalWorship, Tamil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocalWorship Context triple: [Chakrapani Temple, languageOfLocalWorship, Tamil]
-
A.
languageOfWorship
chosen
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
B.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
C.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df6d76dc8190bd8d481fed3225d9 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.