Triple
T35480756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jageshwar group of temples (restorations and additions) |
E1025463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | temple restoration project |
C33178
|
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 restoration project Context triple: [Jageshwar group of temples (restorations and additions), instanceOf, temple restoration project]
-
A.
church restoration project
A church restoration project is an organized effort to repair, preserve, and sometimes modernize a church building while respecting and maintaining its historical, architectural, and spiritual significance.
-
B.
church rebuilding project
A church rebuilding project is a coordinated effort to restore, reconstruct, or significantly renovate a church’s physical structure and facilities, often driven by structural needs, historical preservation, or community growth.
-
C.
temple ruin
A temple ruin is the remains of a once-sacred religious structure, now partially collapsed or eroded, that still conveys its original spiritual and architectural significance.
-
D.
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.
-
E.
architectural reconstruction project
chosen
An architectural reconstruction project is a coordinated effort to research, design, and rebuild a damaged or lost structure to restore its historical, functional, or aesthetic integrity.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.