Triple
T10596818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiprock, New Mexico |
E250135
|
entity |
| Predicate | geologicContextNearby |
P52075
|
FINISHED |
| Object | volcanic monadnock |
—
|
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: volcanic monadnock | Statement: [Shiprock, New Mexico, geologicContextNearby, volcanic monadnock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicContextNearby Context triple: [Shiprock, New Mexico, geologicContextNearby, volcanic monadnock]
-
A.
nearGeologicalSite
chosen
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
B.
regionalGeologyContext
Indicates the broader geological setting or framework within which a specific geological feature, event, or observation occurs.
-
C.
geomorphologicalContext
Indicates the geomorphological setting or landform context in which a feature, process, or observation occurs (e.g., valley, plateau, coastal dune).
-
D.
nearbyBasin
Indicates that one basin is located close to another basin in space.
-
E.
typicalGeologicEnvironment
Indicates the characteristic geologic setting or conditions in which something (such as a rock, mineral, or process) most commonly occurs or forms.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278dacc4819089b759744f100e5f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.