Triple
T22987064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weber segment |
E571937
|
entity |
| Predicate | hasEarthquakeRiskLevel |
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: [Weber segment, hasEarthquakeRiskLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarthquakeRiskLevel Context triple: [Weber segment, hasEarthquakeRiskLevel, high]
-
A.
earthquakeHazardLevel
chosen
Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
-
B.
geologicHazardLevel
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
-
C.
earthquakeDamageLevel
Indicates the severity or extent of damage caused by an earthquake to a given subject.
-
D.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829a96b8819082e0c6d7fb5d018f |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.