Triple
T35256227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prasat Hin Phimai |
E1018239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Khmer temple complex |
C39542
|
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: Khmer temple complex Context triple: [Prasat Hin Phimai, instanceOf, Khmer temple complex]
-
A.
Angkor monument
An Angkor monument is a large-scale architectural and sculptural structure from the Angkor civilization, typically serving religious, ceremonial, or commemorative functions within the Khmer Empire’s temple complexes.
-
B.
Angkor temple
chosen
An Angkor temple is a monumental religious complex built by the Khmer Empire, characterized by intricate stone carvings, towering spires, and symbolic layouts aligned with Hindu-Buddhist cosmology.
-
C.
Buddhist temple–pagoda complex
A Buddhist temple–pagoda complex is a religious architectural ensemble that combines worship halls, monastic quarters, and one or more pagodas serving as reliquaries, symbolic cosmic axes, and focal points for ritual and pilgrimage.
-
D.
temple site
A temple site is a designated area that contains the physical structures, sacred spaces, and associated features of a temple used for religious or spiritual activities.
-
E.
Dvaravati site
A Dvaravati site is an archaeological location associated with the Dvaravati culture (c. 6th–11th centuries CE) in central Thailand, characterized by early Buddhist monuments, distinctive art and architecture, and material remains reflecting Mon-speaking communities and regional trade networks.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.