Triple
T31465757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori Land Online information system |
E802716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land information system |
C59939
|
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: land information system Context triple: [Māori Land Online information system, instanceOf, land information system]
-
A.
land use case
A land use case is a specific scenario or application that illustrates how a particular area of land is designated, managed, and regulated for activities such as residential, commercial, agricultural, industrial, or recreational purposes.
-
B.
land description framework
A land description framework is a structured system for defining, organizing, and communicating the boundaries, characteristics, and legal attributes of parcels of land.
-
C.
cadastral survey system
A cadastral survey system is a coordinated framework of tools, processes, and records used to accurately measure, map, and manage land parcel boundaries, ownership, and related legal rights.
-
D.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
-
E.
geographic information science center
A geographic information science center is a specialized facility or organization dedicated to the research, development, education, and application of geospatial technologies and spatial analysis methods to address geographic and societal challenges.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:23 p.m.