Triple
T31465758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori Land Online information system |
E802716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government digital service |
C32089
|
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: government digital service Context triple: [Māori Land Online information system, instanceOf, government digital service]
-
A.
digital services organization
chosen
A digital services organization is an entity that designs, builds, and operates technology-enabled solutions—such as software platforms, applications, and online services—to deliver value and outcomes for customers and stakeholders.
-
B.
e-government program
An e-government program is an organized initiative that uses digital technologies to deliver public services, enhance government operations, and improve interaction between government, citizens, and businesses.
-
C.
government cloud
A government cloud is a specialized cloud computing environment designed to meet the stringent security, compliance, and operational requirements of public sector agencies for hosting and managing their data and applications.
-
D.
Public service
Public service is the provision of essential goods, support, and regulatory functions by government or community organizations to promote the well-being, safety, and equitable treatment of the public.
-
E.
government operation
Government operation is the coordinated set of activities, processes, and procedures through which a government implements laws, delivers public services, and manages public resources to achieve policy objectives.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:23 p.m.