Triple
T10316768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Geological Survey hydrologic unit codes |
E242036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial identifier system |
C3353
|
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 identifier system Context triple: [United States Geological Survey hydrologic unit codes, instanceOf, geospatial identifier system]
-
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.
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.
-
C.
geographic code
chosen
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
D.
globally unique identifier
A globally unique identifier is a value, typically a long numeric or alphanumeric string, that is guaranteed (or practically guaranteed) to be unique across all systems, times, and contexts for reliably identifying an entity.
-
E.
geodetic coordinate system
A geodetic coordinate system is a reference framework that specifies locations on or near the Earth's surface using latitude, longitude, and often height relative to a defined ellipsoidal model of the Earth.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:49 a.m.