Triple
T37322566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Auckland campus network |
E926520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enterprise network |
C16829
|
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: enterprise network Context triple: [University of Auckland campus network, instanceOf, enterprise network]
-
A.
corporate office network
chosen
A corporate office network is an interconnected system of computers, servers, devices, and communication technologies within an organization that enables secure data sharing, collaboration, and access to internal and external resources.
-
B.
enterprise computer system
An enterprise computer system is an integrated, large-scale computing environment that supports an organization's core business processes, data management, and communication needs across multiple departments and locations.
-
C.
commercial network
A commercial network is a structured system of interconnected businesses, intermediaries, and channels that facilitate the exchange, distribution, and promotion of goods and services in a market.
-
D.
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.
-
E.
global computer network
A global computer network is a worldwide system of interconnected computers and devices that communicate using standardized protocols to share data and resources across vast distances.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.