Triple
T26092640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA IPv6 Special-Purpose Address Registry |
E658167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IP address registry |
C27871
|
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: IP address registry Context triple: [IANA IPv6 Special-Purpose Address Registry, instanceOf, IP address registry]
-
A.
Internet standard registry
An Internet standard registry is an authoritative, publicly maintained catalog that assigns and documents unique identifiers, parameters, and values used in Internet protocols to ensure global interoperability and consistency.
-
B.
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.
-
C.
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.
-
D.
Internet infrastructure database
A centralized repository that stores, organizes, and manages detailed information about the components, configurations, and relationships of internet infrastructure such as networks, servers, domains, and routing resources.
-
E.
technical registry
chosen
A technical registry is a structured system or database that records, manages, and maintains authoritative information about technical entities such as standards, configurations, components, or services.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:48 p.m.