Triple
T2849781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Rhine metropolitan region |
E63064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational metropolitan region |
C7342
|
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: transnational metropolitan region Context triple: [Upper Rhine metropolitan region, instanceOf, transnational metropolitan region]
-
A.
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.
-
B.
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.
-
C.
transboundary region
chosen
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.
-
D.
transnational community
A transnational community is a network of people who maintain enduring social, economic, political, and cultural ties across national borders, creating a shared sense of belonging that spans multiple countries.
-
E.
regional city
A regional city is a mid-sized urban center that serves as an administrative, economic, and cultural hub for its surrounding geographic area, typically outside a nation's primary metropolitan regions.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.