Triple
T28477213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomous Monastic State of the Holy Mountain |
E720595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | self-governed region |
C32151
|
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: self-governed region Context triple: [Autonomous Monastic State of the Holy Mountain, instanceOf, self-governed region]
-
A.
self-governing territory
A self-governing territory is a geographically defined area that exercises autonomous control over its internal affairs under its own local government, while remaining formally subject to a larger sovereign state.
-
B.
semi-autonomous territory
A semi-autonomous territory is a region within a sovereign state that possesses limited self-governing powers and administrative independence while remaining ultimately subject to the authority and constitution of the central government.
-
C.
non-self-governing territory
A non-self-governing territory is a geographic area under the administrative control of another state where the local population has not yet achieved full self-government or independence.
-
D.
autonomous oblast
An autonomous oblast is a type of administrative division within a country that possesses a degree of self-governance and cultural or political autonomy, typically established to recognize and accommodate a specific ethnic or regional group.
-
E.
autonomous area
chosen
An autonomous area is a geographically defined region that possesses a degree of self-governance and decision-making authority independent from the central governing body.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:53 a.m.