Triple
T31276960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Duffer Peak |
E797545
|
entity |
| Predicate | cartographicScaleClass |
P63248
|
FINISHED |
| Object | large-scale map |
—
|
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: large-scale map | Statement: [USGS Duffer Peak, cartographicScaleClass, large-scale map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicScaleClass Context triple: [USGS Duffer Peak, cartographicScaleClass, large-scale map]
-
A.
mapScaleCategory
chosen
Indicates the classification of a map based on its scale range or level of detail.
-
B.
cartographicStandard
Indicates that something conforms to, is defined by, or is governed by a particular cartographic standard or specification.
-
C.
cartographicType
Indicates the specific kind or category of cartographic representation associated with an entity (e.g., map type or mapping style).
-
D.
cartographicFormat
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
E.
cartographicNotation
Indicates the specific symbols, labels, or graphical conventions used to represent geographic features or spatial information 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.