Triple
T22699059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokoharjo cultural landscape |
E561263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Javanese settlement |
C14799
|
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: traditional Javanese settlement Context triple: [Bokoharjo cultural landscape, instanceOf, traditional Javanese settlement]
-
A.
Moravian settlement
A Moravian settlement is a planned religious community established by the Moravian Church, characterized by communal living, shared economic enterprises, and a strong emphasis on worship, education, and missionary work.
-
B.
Indigenous dwelling
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.
-
C.
village-like settlement
chosen
A village-like settlement is a small, closely-knit residential community with limited infrastructure, where inhabitants live in close proximity and often share local resources, traditions, and social ties.
-
D.
Native village
A native village is a small, traditionally organized settlement inhabited primarily by an indigenous community, reflecting its cultural, social, and economic practices.
-
E.
traditional Sasak architectural structure
A traditional Sasak architectural structure is a vernacular building from Lombok, Indonesia, characterized by elevated bamboo or wooden frames, thatched roofs, and spatial layouts reflecting indigenous social, spiritual, and environmental values.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:15 p.m.