Triple
T28390119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association of Asia Pacific Physical Societies |
E719130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional federation |
C31387
|
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 federation Context triple: [Association of Asia Pacific Physical Societies, instanceOf, regional federation]
-
A.
regional federation of political parties
A regional federation of political parties is an alliance of multiple political parties from different countries within a specific geographic region that coordinate policies, strategies, and representation to advance shared ideological or regional interests.
-
B.
regional organisation
chosen
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.
-
C.
federation
A federation is a political or organizational structure in which multiple semi-autonomous entities unite under a central authority while retaining certain independent powers.
-
D.
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.
-
E.
regional trade union
A regional trade union is an organization that represents and advocates for the collective interests, rights, and working conditions of workers within a specific geographic region or group of neighboring countries.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:13 a.m.