Triple
T32518591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIRA |
E831122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Internet Registration Authority |
C35615
|
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: Canadian Internet Registration Authority Context triple: [CIRA, instanceOf, Canadian Internet Registration Authority]
-
A.
Regional Internet Registry
A Regional Internet Registry is an organization responsible for allocating, registering, and managing Internet number resources (such as IP addresses and AS numbers) within a specific geographic region.
-
B.
national internet registry
chosen
A national internet registry is an organization responsible for allocating and managing internet number resources (such as IP addresses and AS numbers) within a specific country or territory, typically under the broader coordination of a regional internet registry.
-
C.
ICANN region
An ICANN region is a geographically defined area used by the Internet Corporation for Assigned Names and Numbers to organize and balance global representation in internet governance and policy-making.
-
D.
Canadian NORAD Region
The Canadian NORAD Region is the division of the North American Aerospace Defense Command responsible for aerospace warning, control, and defense operations over Canadian territory and adjacent airspace.
-
E.
ICANN structure element
An ICANN structure element is a component within the organizational framework of the Internet Corporation for Assigned Names and Numbers, such as supporting organizations, advisory committees, or stakeholder groups, that participates in the development and implementation of global internet naming and addressing policies.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.