Triple
T31053961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Systems Consortium |
E791344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet infrastructure organization |
C60777
|
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 organization Context triple: [Internet Systems Consortium, instanceOf, Internet infrastructure organization]
-
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.
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.
-
C.
institutional network
An institutional network is a structured web of interconnected organizations and agencies that collaborate, share resources, and coordinate activities to achieve common goals or fulfill complementary roles within a broader system.
-
D.
network architecture
A network architecture is the structured design and organization of hardware, software, protocols, and communication paths that define how data flows and services are delivered within a computer network.
-
E.
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.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9 p.m.