Triple
T34864620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroregions |
E1004977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border cooperative structure |
C15734
|
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 cooperative structure Context triple: [Euroregions, instanceOf, cross-border cooperative structure]
-
A.
cross-border institution
chosen
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
-
B.
cross‑border operation
A cross-border operation is an organized activity or transaction conducted across the legal, regulatory, or geographic boundaries of two or more countries.
-
C.
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.
-
D.
cross-border investment channel
A cross-border investment channel is a structured mechanism or platform that enables the flow of capital between investors and assets located in different countries, while managing regulatory, currency, and operational complexities.
-
E.
customs cooperation body
A customs cooperation body is an organization or institutional mechanism through which customs authorities from different jurisdictions coordinate policies, share information, and collaborate on enforcement to facilitate legitimate trade and combat customs-related violations.
- 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.