Triple
T33437394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLD |
E856267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cartographic styling language |
C38292
|
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: cartographic styling language Context triple: [SLD, instanceOf, cartographic styling language]
-
A.
cartographic specification
chosen
A cartographic specification is a detailed set of rules and standards that defines how geographic data should be symbolized, generalized, and presented in a map to meet specific communication and design objectives.
-
B.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
-
C.
cartographic regulation
Cartographic regulation is the set of rules, standards, and policies that govern how geographic information is selected, represented, and distributed on maps to ensure accuracy, consistency, and ethical use.
-
D.
geographic information standard series
A geographic information standard series is a coordinated set of related standards that define consistent models, formats, and procedures for representing, exchanging, and managing geographic information.
-
E.
geospatial data standard framework
A geospatial data standard framework is a structured set of guidelines, models, and protocols that ensure consistent representation, exchange, and interoperability of location-based data across systems and organizations.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.