Triple
T31081459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN North America region |
E792104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ICANN region |
C58820
|
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: ICANN region Context triple: [ICANN North America region, instanceOf, ICANN region]
-
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.
International Telecommunication Union region
An International Telecommunication Union region is a geographically defined area of the world established by the ITU to coordinate and standardize the use of the radio-frequency spectrum and satellite orbits among member countries.
-
C.
affiliate of ICANN
An affiliate of ICANN is an organization or entity formally associated with the Internet Corporation for Assigned Names and Numbers to support its mission, programs, or policy development activities without being part of its core governing structure.
-
D.
national internet registry
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.
-
E.
ICAO region
An ICAO region is a geographically defined area of the world used by the International Civil Aviation Organization to organize and manage international air navigation, air traffic services, and aviation standards.
- F. None of above. chosen
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.