Triple
T20495552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Mount Drum |
E502862
|
entity |
| Predicate | cartographicMaterial |
P97483
|
FINISHED |
| Object | topographic data |
—
|
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: topographic data | Statement: [USGS Mount Drum, cartographicMaterial, topographic data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicMaterial Context triple: [USGS Mount Drum, cartographicMaterial, topographic data]
-
A.
cartographicWork
Indicates a relationship where one entity is a cartographic work (such as a map or chart) that represents geographic information about another entity.
-
B.
cartographicSource
chosen
Indicates the map, chart, or other cartographic resource from which the described information or representation is derived.
-
C.
cartographicUse
Indicates the way in which something is used or intended to be used within a cartographic or map-making context.
-
D.
cartographicFormat
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
E.
cartographicType
Indicates the specific kind or category of cartographic representation associated with an entity (e.g., map type or mapping style).
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbd2dfc81908204f7bfa8a763b6 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.