Triple
T31081383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At-Large Structures in North America |
E792102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional At-Large Structure collection |
C27012
|
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 At-Large Structure collection Context triple: [At-Large Structures in North America, instanceOf, regional At-Large Structure collection]
-
A.
Regional At-Large Organization
chosen
A Regional At-Large Organization is a geographically defined body that represents and coordinates the interests, participation, and activities of individual Internet users and At-Large Structures within a specific region in global Internet governance processes.
-
B.
regional municipal structure
A regional municipal structure is an organized framework that coordinates governance, services, and planning across multiple municipalities within a defined geographic area.
-
C.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
D.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
-
E.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.