Triple
T8799341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Ridgecrest earthquakes |
E209361
|
entity |
| Predicate | mainshockLocalTime |
P22115
|
FINISHED |
| Object | 20:19 PDT |
—
|
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: 20:19 PDT | Statement: [2019 Ridgecrest earthquakes, mainshockLocalTime, 20:19 PDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainshockLocalTime Context triple: [2019 Ridgecrest earthquakes, mainshockLocalTime, 20:19 PDT]
-
A.
mainshockTimeUTC
Indicates the date and time of the primary (main) earthquake event expressed in Coordinated Universal Time (UTC).
-
B.
mainshockDate
Indicates the date on which the primary or largest earthquake event (the mainshock) in a seismic sequence occurred.
-
C.
localTime
chosen
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
D.
endTimeLocal
Indicates the local date and time at which an event, activity, or state concludes.
-
E.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
- 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.