Triple
T17138364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumah Gadang |
E415898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minangkabau traditional house |
C21280
|
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: Minangkabau traditional house Context triple: [Rumah Gadang, instanceOf, Minangkabau traditional house]
-
A.
ancestral hall
An ancestral hall is a traditional building or dedicated space used for honoring, worshipping, and commemorating a family’s ancestors through rituals, tablets, and memorial displays.
-
B.
Ryukyuan architectural structure
A Ryukyuan architectural structure is a traditional building or construction from the Ryukyu Islands characterized by red-tiled roofs, stone walls, wooden frameworks, and design elements adapted to the subtropical climate and local cultural practices.
-
C.
Indigenous dwelling
chosen
An Indigenous dwelling is a traditional, culturally specific structure designed and built by Indigenous peoples using locally available materials to provide shelter, support community life, and embody spiritual and environmental relationships.
-
D.
Minangkabau royal dynasty
The Minangkabau royal dynasty is the traditional ruling lineage of the Minangkabau people of West Sumatra, Indonesia, historically governing through a matrilineal adat system that blended indigenous customs with Islamic influences.
-
E.
traditional Japanese residence
A traditional Japanese residence is a wooden, often single-story home characterized by tatami-mat rooms, sliding shoji doors, engawa verandas, and a close integration with nature and seasonal changes.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.