Triple
T20216726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Congo (as associated territory) |
E495146
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | associated territory |
C8394
|
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: associated territory Context triple: [Belgian Congo (as associated territory), instanceOf, associated territory]
-
A.
overseas territory
An overseas territory is a geographically separate and often distant region that is under the sovereignty or jurisdiction of a country but not fully integrated as part of its main national territory.
-
B.
incorporated territory of the United States
An incorporated territory of the United States is a region under U.S. sovereignty that is considered an integral part of the country for constitutional purposes, though it has not yet achieved statehood.
-
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.
former dependent territory
chosen
A former dependent territory is a geographic area that was once politically, economically, or administratively controlled by another sovereign state but has since gained independence or a different political status.
-
E.
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.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:39 p.m.