Triple
T6785815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distrito Nacional |
E155799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special administrative district |
C20215
|
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 administrative district Context triple: [Distrito Nacional, instanceOf, special administrative district]
-
A.
special administrative division
chosen
A special administrative division is a distinct territorial unit within a country that has unique legal, political, or administrative status differing from that of regular administrative regions.
-
B.
special autonomous region
A special autonomous region is a subnational territorial unit granted a high degree of self-governance and legislative autonomy distinct from other administrative divisions within the same country.
-
C.
Special Administrative Region of China
A Special Administrative Region of China is a highly autonomous territorial unit under Chinese sovereignty that maintains its own legal, economic, and administrative systems distinct from those of mainland China.
-
D.
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.
-
E.
island district
An island district is an administrative or urban area composed primarily of one or more islands, often characterized by geographic separation from the mainland and distinct local governance, infrastructure, and community identity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.