Triple
T1918844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomous Administration of North and East Syria |
E40079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | de facto autonomous region |
C2839
|
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: de facto autonomous region Context triple: [Autonomous Administration of North and East Syria, instanceOf, de facto autonomous region]
-
A.
self-governing territory
chosen
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.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
C.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
D.
federal territory
A federal territory is a geographic area under the direct jurisdiction and administration of a federal government, distinct from constituent states or provinces and typically lacking the same degree of self-governance.
-
E.
state-like entity
A state-like entity is an abstraction that encapsulates a distinct configuration of conditions or behaviors within a system, often determining how the system responds to inputs at a given time.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.