Triple
T29276945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEDA |
E742269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | socioeconomic planning agency |
C2948
|
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: socioeconomic planning agency Context triple: [NEDA, instanceOf, socioeconomic planning agency]
-
A.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
B.
planning agency
A planning agency is an organization responsible for developing, coordinating, and regulating plans and policies to guide land use, infrastructure, and community development within a specific jurisdiction.
-
C.
planning commission
A planning commission is a governmental or advisory body responsible for reviewing, guiding, and making recommendations on land use, development proposals, and long-term community planning policies.
-
D.
economic development agency
chosen
An economic development agency is an organization, typically public or public–private, that designs and implements programs to attract investment, support businesses, and promote sustainable economic growth within a specific region.
-
E.
Commission for Social Development
The Commission for Social Development is a functional commission of the United Nations Economic and Social Council responsible for advising on and promoting policies that advance social development, including poverty eradication, full employment, and social integration worldwide.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:51 p.m.