Triple
T14530589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Coast Ranges seismicity |
E340901
|
entity |
| Predicate | typicalFocalDepthRange |
P114643
|
FINISHED |
| Object | 0–20 km |
—
|
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: 0–20 km | Statement: [California Coast Ranges seismicity, typicalFocalDepthRange, 0–20 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFocalDepthRange Context triple: [California Coast Ranges seismicity, typicalFocalDepthRange, 0–20 km]
-
A.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
earthquakeMagnitudeRange
Indicates the range of magnitudes within which an earthquake’s measured strength falls.
-
C.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
-
D.
earthquakeType
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
-
E.
tectonicActivityCharacteristic
Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea052d01c81909c8592c351be6f35 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.