Triple
T19812596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badrinath-Kedarnath Temple Committee |
E475982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | temple management committee |
C34267
|
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: temple management committee Context triple: [Badrinath-Kedarnath Temple Committee, instanceOf, temple management committee]
-
A.
temple
A temple is a dedicated sacred structure or space where individuals or communities engage in worship, rituals, and spiritual practices associated with a particular religion or belief system.
-
B.
gurdwara management committee
A gurdwara management committee is a governing body responsible for overseeing the administration, religious activities, finances, and community services of a Sikh place of worship.
-
C.
religious organization committee
chosen
A religious organization committee is a structured group within a faith-based institution responsible for planning, coordinating, and overseeing specific religious, administrative, or community activities in alignment with the organization’s beliefs and goals.
-
D.
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.
-
E.
temple tower
A temple tower is a tall, often ornate vertical structure that rises above a temple complex, symbolizing spiritual ascent and serving as a prominent architectural and religious landmark.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.