Triple
T26906324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIAZA (associate/partner in European context) |
E677264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional partner body |
C11923
|
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 partner body Context triple: [BIAZA (associate/partner in European context), instanceOf, regional partner body]
-
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.
partnership body
A partnership body is an organized group formed by two or more independent entities that collaborate under agreed arrangements to pursue shared goals, responsibilities, and benefits.
-
C.
regional body of an international organization
chosen
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
-
D.
regional representative group
A regional representative group is an organized body of individuals chosen or appointed to advocate for and make decisions on behalf of stakeholders within a specific geographic area.
-
E.
regional electoral body
A regional electoral body is an organization responsible for administering, supervising, and ensuring the integrity of elections within a specific subnational geographic area.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:59 a.m.