Triple
T24618650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Mount Sanford A-4 |
E609341
|
entity |
| Predicate | mapGrid |
P156765
|
FINISHED |
| Object | USGS quadrangle grid |
—
|
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: USGS quadrangle grid | Statement: [USGS Mount Sanford A-4, mapGrid, USGS quadrangle grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapGrid Context triple: [USGS Mount Sanford A-4, mapGrid, USGS quadrangle grid]
-
A.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
-
B.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
C.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
-
D.
mapsDepict
Indicates that maps visually represent or illustrate the geographic features, locations, or spatial relationships of something.
-
E.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
- F. None of above. chosen
Provenance (4 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.