Triple
T34864668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpathian Euroregion |
E1004978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational cooperative 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 cooperative region Context triple: [Carpathian Euroregion, instanceOf, transnational cooperative region]
-
A.
binational urban region
A binational urban region is a contiguous metropolitan area that spans across the borders of two countries, integrating economic, social, and infrastructural systems while operating under dual national jurisdictions.
-
B.
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.
-
C.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
D.
regional cooperation bloc
A regional cooperation bloc is an alliance of neighboring countries that coordinate policies and collaborate on economic, political, or security issues to advance shared regional interests.
-
E.
transnational organization
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.