Triple
T3698613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinshasa–Brazzaville metropolitan area |
E78518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transborder metropolitan area |
C7343
|
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: transborder metropolitan area Context triple: [Kinshasa–Brazzaville metropolitan area, instanceOf, transborder metropolitan area]
-
A.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
-
B.
cross-border area
chosen
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
C.
metropolitan area
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
-
D.
transcontinental city
A transcontinental city is an urban area whose continuous metropolitan territory spans across two or more continents, often divided by a major geographic boundary such as a strait, sea, or continental border.
-
E.
international border point
An international border point is a designated location where people, goods, and vehicles legally cross from one country into another under the control of official authorities.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.