Triple
T29972534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baduy village |
E761357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sundanese settlement |
C56604
|
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: Sundanese settlement Context triple: [Baduy village, instanceOf, Sundanese settlement]
-
A.
Sundanese polity
A Sundanese polity is a socio-political entity formed by Sundanese communities in western Java, historically characterized by shared language, culture, customary law, and governance structures ranging from local chiefdoms to centralized kingdoms.
-
B.
Minangkabau customary territory
Minangkabau customary territory is the traditional socio-cultural and ancestral land domain of the Minangkabau people, defined by their matrilineal adat (customary law), communal land rights, and shared cultural identity rather than formal administrative boundaries.
-
C.
Makassarese kingdom
The Makassarese kingdom was a historical maritime polity centered in South Sulawesi, Indonesia, known for its powerful trading ports, Islamic influence, and resistance to European colonial expansion in the early modern period.
-
D.
Andamanese people
Andamanese people are the indigenous inhabitants of the Andaman Islands in the Bay of Bengal, comprising several distinct groups with unique languages, cultures, and histories, many of whom have traditionally lived as hunter-gatherers.
-
E.
Balinese polity
A Balinese polity is a traditional socio-political entity in Bali characterized by a hierarchical kingship, ritual authority, and complex relationships between royal courts, villages, and religious institutions.
- F. None of above. chosen
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:32 p.m.