Triple
T4267404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayward Fault |
E96858
|
entity |
| Predicate | seismicRiskLevel |
P34010
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Hayward Fault, seismicRiskLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seismicRiskLevel Context triple: [Hayward Fault, seismicRiskLevel, high]
-
A.
earthquakeHazardLevel
chosen
Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
-
B.
geologicalHazardZoneFor
Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
-
C.
seismicSafetyConcernsIdentified
Indicates that potential risks or issues related to seismic safety have been detected or recognized.
-
D.
relatedEarthquakeZone
Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
-
E.
hasNaturalHazardRisk
Indicates that an entity is exposed or subject to potential damage or impact from one or more natural hazards (e.g., earthquakes, floods, storms).
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.