Triple
T5984344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Asian Dragons |
E133189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic grouping |
C2010
|
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 economic grouping Context triple: [Four Asian Dragons, instanceOf, regional economic grouping]
-
A.
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.
-
B.
Economic alliance
chosen
An economic alliance is a formal or informal partnership between countries or regions designed to promote mutual economic benefits through cooperation in trade, investment, and financial policies.
-
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.
MERCOSUR institution
A MERCOSUR institution is an organizational body within the Southern Common Market (MERCOSUR) framework responsible for formulating, coordinating, or implementing policies and decisions that govern regional economic, political, and social integration among member states.
-
E.
MERCOSUR organ
A MERCOSUR organ is an institutional body within the Southern Common Market (MERCOSUR) responsible for decision-making, coordination, implementation, or advisory functions related to the bloc’s regional integration policies and agreements.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.