Triple
T295900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada West Coast |
E6091
|
entity |
| Predicate | hasSeismicActivity |
P8807
|
FINISHED |
| Object | frequent earthquakes |
—
|
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: frequent earthquakes | Statement: [Canada West Coast, hasSeismicActivity, frequent earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeismicActivity Context triple: [Canada West Coast, hasSeismicActivity, frequent earthquakes]
-
A.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
B.
tectonicActivityCharacteristic
chosen
Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
-
C.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
D.
earthquakeMagnitude
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
E.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.