Triple
T8799340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Ridgecrest earthquakes |
E209361
|
entity |
| Predicate | foreshockDate |
P12072
|
FINISHED |
| Object | 2019-07-04 |
—
|
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: 2019-07-04 | Statement: [2019 Ridgecrest earthquakes, foreshockDate, 2019-07-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreshockDate Context triple: [2019 Ridgecrest earthquakes, foreshockDate, 2019-07-04]
-
A.
foreshocks
Indicates that an earthquake occurs as a smaller, preceding seismic event that happens before a larger mainshock in the same region.
-
B.
earthquakeDate
chosen
Indicates the specific calendar date on which an earthquake event occurred.
-
C.
earthquakeDateRespondedTo
Indicates the date on which a response or action was taken in relation to a specific earthquake event.
-
D.
seismicEvent
Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
-
E.
earthquakeSequence
Indicates a relationship where multiple earthquakes are linked as part of the same temporal or causal sequence of seismic events.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb7491c8190bcdb98d6cc003d9e |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.