Triple
T1153760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crescent City, California |
E23734
|
entity |
| Predicate | frequentNaturalHazard |
P25357
|
FINISHED |
| Object | tsunamis |
—
|
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: tsunamis | Statement: [Crescent City, California, frequentNaturalHazard, tsunamis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentNaturalHazard Context triple: [Crescent City, California, frequentNaturalHazard, tsunamis]
-
A.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
tectonicEvents
Indicates the occurrence or involvement of entities in geological processes related to the movement and interaction of Earth’s tectonic plates, such as earthquakes, volcanic activity, or continental drift.
-
C.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
D.
volcanicHazards
Indicates the presence or characterization of dangers and harmful phenomena associated with volcanic activity.
-
E.
isLandslide
Indicates that an event or condition involves a landslide, where a mass of earth or rock moves down a slope.
- F. None of above. chosen
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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc8e9cb481908a528a828b21d497 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.