Triple
T32935776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio TriRhena |
E842523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border European region |
C4696
|
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: cross-border European region Context triple: [Regio TriRhena, instanceOf, cross-border European region]
-
A.
cross-border area
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.
-
B.
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.
-
C.
eurodistrict
chosen
A eurodistrict is a cross-border administrative and cooperation entity formed by neighboring local authorities from different European countries to coordinate services, planning, and development in a shared transnational region.
-
D.
outermost region of the European Union
The outermost region of the European Union is a geographically distant territory that is fully part of an EU member state and the EU itself, but benefits from specific measures to address its remoteness, insularity, and economic and social challenges.
-
E.
cross-border institution
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.