Triple
T7026777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Region of Yogyakarta |
E162968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | province-level administrative division |
C20673
|
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: province-level administrative division Context triple: [Special Region of Yogyakarta, instanceOf, province-level administrative division]
-
A.
provincial-level city
A provincial-level city is an urban administrative division that holds the same rank as a province or is directly governed at the provincial level, typically encompassing both a central city and surrounding rural or suburban areas.
-
B.
autonomous prefecture
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
-
C.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
D.
first-level administrative division of the Philippines
A first-level administrative division of the Philippines is a primary local government unit, such as a province, highly urbanized city, or independent component city, directly under the national government and above municipalities and barangays in the administrative hierarchy.
-
E.
prefecture
A prefecture is an administrative division or jurisdiction within a country, typically governed by a prefect and possessing certain local governmental powers.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.