Triple
T11611382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Mapping and Resource Information Authority |
E275391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial information authority |
C18741
|
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: geospatial information authority Context triple: [National Mapping and Resource Information Authority, instanceOf, geospatial information authority]
-
A.
geospatial information unit
A geospatial information unit is a conceptual entity that encapsulates location-based data, attributes, and spatial relationships for a specific geographic feature or area.
-
B.
geographic information committee
A geographic information committee is a coordinated group responsible for overseeing the development, management, sharing, and governance of geographic data and related technologies within an organization or jurisdiction.
-
C.
geospatial intelligence facility
A geospatial intelligence facility is a secure, specialized site where experts collect, process, analyze, and disseminate geographic and imagery data to support military, intelligence, and strategic decision-making.
-
D.
national mapping agency
chosen
A national mapping agency is a government organization responsible for producing, maintaining, and distributing authoritative geographic and cartographic information for an entire country.
-
E.
geospatial web service
A geospatial web service is an online system that provides access to, processing of, and interaction with geographic data and spatial analyses over the web using standardized protocols.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.