Triple
T38188569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyote Creek Fault |
E1005387
|
entity |
| Predicate | hasEarthquakeActivity |
P12618
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Coyote Creek Fault, hasEarthquakeActivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarthquakeActivity Context triple: [Coyote Creek Fault, hasEarthquakeActivity, yes]
-
A.
hasEarthquakes
chosen
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
hasGeologicalActivity
Indicates that an entity exhibits or is associated with ongoing or past geological processes such as volcanism, tectonics, or seismic activity.
-
C.
hasEarlyEarthquakesReportedSince
Indicates that earlier-than-expected earthquakes have been reported starting from a specified point in time.
-
D.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
E.
relatedEarthquakeZone
Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.