Triple
T7026776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Region of Yogyakarta |
E162968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special region of Indonesia |
C4697
|
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: special region of Indonesia Context triple: [Special Region of Yogyakarta, instanceOf, special region of Indonesia]
-
A.
province of Indonesia
chosen
A province of Indonesia is a primary administrative division of the country, each governed by a provincial government headed by a governor and possessing a degree of political and fiscal autonomy under the national framework.
-
B.
subregion of Southeast Asia
A subregion of Southeast Asia is a geographically and culturally defined subset of the broader Southeast Asian area, typically grouped by shared historical, political, economic, or environmental characteristics.
-
C.
regency of Indonesia
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.
-
D.
island province
An island province is an administrative region consisting entirely of one or more islands, geographically separated from a country's mainland but governed as an integral part of the national territory.
-
E.
island province
An island province is a territorial and administrative division of a country that consists entirely of one or more islands, often with distinct geographic, cultural, and economic characteristics shaped by its maritime setting.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.