Triple
T22308896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parshvanath Jain Temple |
E551460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hinduism-related place of worship in India |
C42728
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hinduism-related place of worship in India Context triple: [Parshvanath Jain Temple, instanceOf, Hinduism-related place of worship in India]
-
A.
Hindu monastic institution
A Hindu monastic institution is an organized religious community or center where renunciants (monks and nuns) live under spiritual discipline, pursue scriptural study, meditation, and service, and provide religious guidance to lay followers.
-
B.
Hindu temple group
A Hindu temple group is a collection of Hindu temples, often located in close proximity, that together form a religious complex or pilgrimage center unified by shared deities, rituals, or historical and cultural significance.
-
C.
place in Hindu tradition
chosen
A place in Hindu tradition is a physical or sacred location—such as a temple, pilgrimage site, river, mountain, or city—imbued with religious, mythological, or spiritual significance and associated rituals.
-
D.
Hindu organization
A Hindu organization is a structured group or institution that promotes, practices, preserves, or propagates Hindu religious, cultural, social, or philosophical traditions and values.
-
E.
Hindu denomination
A Hindu denomination is a distinct religious tradition within Hinduism characterized by shared beliefs, practices, scriptures, and devotional focus, often centered on a particular deity or philosophical school.
- F. None of above.
Provenance (1 batch)
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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.