Triple
T36471538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NELSAP-CU |
E898550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional coordination unit |
C66027
|
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 coordination unit Context triple: [NELSAP-CU, instanceOf, regional coordination unit]
-
A.
regional committee
A regional committee is a group of appointed or elected representatives from a specific geographic area who collaborate to make decisions, coordinate activities, and provide governance or oversight on issues affecting that region.
-
B.
regional governmental organization
A regional governmental organization is a formal body composed of multiple neighboring countries or subnational entities within a specific geographic area that collaborates to coordinate policies, manage shared interests, and address common regional issues.
-
C.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
D.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
E.
regional analytical office
A regional analytical office is an organizational unit responsible for collecting, processing, and interpreting data within a specific geographic area to support decision-making and strategic planning.
- F. None of above. chosen
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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.