Triple
T14491086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garbhagriha |
E359363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu temple component |
C20598
|
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: Hindu temple component Context triple: [Garbhagriha, instanceOf, Hindu temple component]
-
A.
Hindu monastery
A Hindu monastery is a religious community and residence where Hindu monks live, study scriptures, practice spiritual disciplines, and guide devotees in accordance with specific traditions or lineages.
-
B.
component of Sikh gurdwara
A component of a Sikh gurdwara is any architectural, functional, or symbolic element—such as the prayer hall, langar hall, Nishan Sahib, or sarovar—that collectively supports Sikh worship, community service, and spiritual practice.
-
C.
temple architecture
chosen
Temple architecture is the conceptual class encompassing the design principles, structural elements, symbolic forms, and spatial organization used to create sacred buildings for worship across different cultures and historical periods.
-
D.
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.
-
E.
component of palace complex
A component of a palace complex is an individual architectural or functional unit—such as a hall, courtyard, gate, garden, or residential wing—that contributes to the overall structure, use, and symbolism of the palace ensemble.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.