Triple
T20246644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountain fault system |
E498440
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | San Juan Mountains faults |
—
|
NE NERFINISHED |
How this triple was built (3 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: San Juan Mountains faults | Statement: [Rocky Mountain fault system, hasComponent, San Juan Mountains faults]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: San Juan Mountains faults Context triple: [Rocky Mountain fault system, hasComponent, San Juan Mountains faults]
-
A.
Panamint Valley fault zone
The Panamint Valley fault zone is a major strike-slip fault system in eastern California that accommodates significant crustal deformation and helps shape the tectonically active Panamint Valley region.
-
B.
Calico–Hidalgo fault zone
The Calico–Hidalgo fault zone is a major strike-slip fault system in the Mojave Desert of Southern California that accommodates part of the region’s tectonic shear between the Pacific and North American plates.
-
C.
Rocky Mountain fault system
The Rocky Mountain fault system is a major network of geological faults along the Rocky Mountains that has shaped the region’s topography and tectonic evolution.
-
D.
Wasatch Fault
The Wasatch Fault is a major active normal fault system in Utah that poses significant earthquake risk to the densely populated Wasatch Front region.
-
E.
Motagua–Polochic fault system
The Motagua–Polochic fault system is a major left-lateral strike-slip fault zone in Central America that accommodates tectonic motion between the North American and Caribbean plates and is a significant source of regional seismic activity.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: San Juan Mountains faults Target entity description: The San Juan Mountains faults are a network of geological fractures and fault zones in southwestern Colorado that have shaped the rugged topography and volcanic history of the San Juan Mountains.
-
A.
Panamint Valley fault zone
The Panamint Valley fault zone is a major strike-slip fault system in eastern California that accommodates significant crustal deformation and helps shape the tectonically active Panamint Valley region.
-
B.
Calico–Hidalgo fault zone
The Calico–Hidalgo fault zone is a major strike-slip fault system in the Mojave Desert of Southern California that accommodates part of the region’s tectonic shear between the Pacific and North American plates.
-
C.
Rocky Mountain fault system
The Rocky Mountain fault system is a major network of geological faults along the Rocky Mountains that has shaped the region’s topography and tectonic evolution.
-
D.
Wasatch Fault
The Wasatch Fault is a major active normal fault system in Utah that poses significant earthquake risk to the densely populated Wasatch Front region.
-
E.
Motagua–Polochic fault system
The Motagua–Polochic fault system is a major left-lateral strike-slip fault zone in Central America that accommodates tectonic motion between the North American and Caribbean plates and is a significant source of regional seismic activity.
- F. None of above. chosen
Provenance (2 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a3c61481909413e042d76cc580 |
completed | April 20, 2026, 6:42 p.m. |
Created at: April 11, 2026, 11:40 p.m.