Triple
T30113173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunnan–Myanmar border economic cooperation zone |
E765341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border economic cooperation zone |
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: border economic cooperation zone Context triple: [Yunnan–Myanmar border economic cooperation zone, instanceOf, border economic cooperation zone]
-
A.
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.
-
B.
tariff zone
A tariff zone is a defined geographic area within which specific pricing rules, rates, or charges apply for goods, services, or transportation.
-
C.
special economic zone
A special economic zone is a designated geographic area within a country where business and trade laws differ from the rest of the nation to attract investment, boost exports, and stimulate economic growth.
-
D.
regional economic zone
A regional economic zone is a geographically defined area within or across countries where economic policies, regulations, and incentives are coordinated to promote trade, investment, and development.
-
E.
border junction
A border junction is a point or area where the boundaries of two or more distinct regions, territories, or systems meet and interact.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:11 p.m.