Triple
T33735766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Mekong Subregion transport network |
E864409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional cooperation project |
C56955
|
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: regional cooperation project Context triple: [Greater Mekong Subregion transport network, instanceOf, regional cooperation project]
-
A.
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.
-
B.
territorial cooperation programme
chosen
A territorial cooperation programme is a coordinated framework of policies, projects, and funding mechanisms designed to foster collaboration across regions or borders to address shared challenges and promote balanced territorial development.
-
C.
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.
-
D.
regional economic cooperation framework
A regional economic cooperation framework is an organized arrangement among neighboring countries to coordinate policies, reduce trade and investment barriers, and promote shared economic development and integration.
-
E.
regional currency project
A regional currency project is an initiative to design, implement, and manage a complementary monetary system used within a specific geographic area to support local economic activity, resilience, and community goals.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.