Triple
T34933263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerson fault |
E1007499
|
entity |
| Predicate | associatedWithEarthquake |
P38434
|
FINISHED |
| Object | 1992 Landers earthquake |
E1007500
|
NE 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: 1992 Landers earthquake | Statement: [Emerson fault, associatedWithEarthquake, 1992 Landers earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEarthquake Context triple: [Emerson fault, associatedWithEarthquake, 1992 Landers earthquake]
-
A.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
relatedEarthquakeZone
chosen
Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
-
C.
earthquakeType
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
-
D.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
-
E.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
- F. None of above.
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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b26447cc8190a75dcc83b3110ef5 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.