Triple
T2121064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crestview USGS topographic map |
E43922
|
entity |
| Predicate | mapFeatureType |
P5048
|
FINISHED |
| Object | topography |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: topography | Statement: [Crestview USGS topographic map, mapFeatureType, topography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapFeatureType Context triple: [Crestview USGS topographic map, mapFeatureType, topography]
-
A.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
arealFeature
Indicates a relationship where something is characterized as a spatial or geographic feature occupying an area on a surface or map.
-
D.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
E.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
- F. None of above.
Provenance (3 batches)
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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3404348190bc843022fbd2b4d0 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.