Triple
T8918682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Routing Registry |
E212356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet infrastructure database |
C25309
|
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: Internet infrastructure database Context triple: [Internet Routing Registry, instanceOf, Internet infrastructure database]
-
A.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
-
B.
infrastructure
Infrastructure is the foundational physical and organizational systems—such as transportation, utilities, communication networks, and public facilities—that enable a society or organization to function and grow.
-
C.
internet access project
An internet access project is an initiative designed to plan, deploy, and manage the infrastructure and services needed to provide reliable, affordable connectivity to targeted users or communities.
-
D.
Internet access toolkit
A comprehensive set of hardware, software, and configuration utilities that enables users or systems to establish, manage, and troubleshoot connections to the internet.
-
E.
transportation database
A transportation database is a structured collection of data that stores, organizes, and manages information related to transportation systems, such as routes, vehicles, schedules, and passenger or cargo records, to support planning, operations, and analysis.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.