Triple
T1269256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascadia Subduction Zone |
E15671
|
entity |
| Predicate | lastKnownGreatEarthquakeDate |
P12072
|
FINISHED |
| Object | January 26, 1700 |
—
|
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: January 26, 1700 | Statement: [Cascadia Subduction Zone, lastKnownGreatEarthquakeDate, January 26, 1700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastKnownGreatEarthquakeDate Context triple: [Cascadia Subduction Zone, lastKnownGreatEarthquakeDate, January 26, 1700]
-
A.
earthquakeDate
chosen
Indicates the specific calendar date on which an earthquake event occurred.
-
B.
earthquakeMagnitude
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
C.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
D.
earthquakeLocalTime
Indicates the local time at which an earthquake event occurred at its specific location.
-
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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c03aaa8c8190bacb7de5a38329da |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.