Triple
T35427079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regency government of Kepulauan Talaud |
E1023949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regency government in Indonesia |
C18078
|
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: regency government in Indonesia Context triple: [Regency government of Kepulauan Talaud, instanceOf, regency government in Indonesia]
-
A.
regency of Indonesia
chosen
A regency of Indonesia is a second-level administrative division, below a province, governed by a regent and responsible for managing local governance, public services, and regional development within its territory.
-
B.
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.
-
C.
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.
-
D.
Indonesian government regulation
An Indonesian government regulation is a legally binding rule issued by authorized state institutions to implement, clarify, or operationalize provisions of higher-level laws within Indonesia’s legal system.
-
E.
Javanese monarchy
A Javanese monarchy is a traditional hierarchical system of kingship in Java that blends indigenous customs, Islamic influences, and courtly culture to legitimize political authority and spiritual power.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.