Triple
T15545120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunei Darussalam Network Information Centre |
E370589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national internet registry |
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: national internet registry Context triple: [Brunei Darussalam Network Information Centre, instanceOf, national internet registry]
-
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.
domain name registry
A domain name registry is an authoritative database and management system that stores, maintains, and administers the records of all domain names registered under a specific top-level domain.
-
C.
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.
-
D.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
E.
technical registry
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. 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:07 a.m.