Triple
T8648978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tây Nguyên communal house |
E205050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage structure |
C10087
|
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: cultural heritage structure Context triple: [Tây Nguyên communal house, instanceOf, cultural heritage structure]
-
A.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
B.
cultural site
chosen
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
C.
cultural heritage
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
-
D.
cultural heritage protection system
A cultural heritage protection system is an integrated framework of policies, technologies, and practices designed to identify, preserve, monitor, and safeguard tangible and intangible cultural assets from damage, loss, or unauthorized exploitation.
-
E.
man_made_structure
A man_made_structure is any constructed physical entity or facility created by humans to serve functional, aesthetic, or protective purposes in the built environment.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.