Triple
T29918165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Searles Valley, California |
E759847
|
entity |
| Predicate | locatedNearEpicenterOf |
P1939
|
FINISHED |
| Object | 2019 Searles Valley earthquake (M6.4) |
—
|
NE NERFINISHED |
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 Searles Valley earthquake (M6.4) | Statement: [Searles Valley, California, locatedNearEpicenterOf, 2019 Searles Valley earthquake (M6.4)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearEpicenterOf Context triple: [Searles Valley, California, locatedNearEpicenterOf, 2019 Searles Valley earthquake (M6.4)]
-
A.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
-
B.
disasterLocation
Indicates the place where a disaster occurs or has its primary impact.
-
C.
epicenter
chosen
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
-
D.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
E.
notableEventFeltArea
Indicates the geographic area in which the effects or impact of a notable event were experienced or perceived.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: April 29, 2026, 6:13 p.m.