Triple
T3250348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Cape Mendocino earthquakes |
E68161
|
entity |
| Predicate | secondEventMagnitude |
P5297
|
FINISHED |
| Object | 6.5 Mw |
—
|
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: 6.5 Mw | Statement: [1992 Cape Mendocino earthquakes, secondEventMagnitude, 6.5 Mw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondEventMagnitude Context triple: [1992 Cape Mendocino earthquakes, secondEventMagnitude, 6.5 Mw]
-
A.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
C.
seismicMoment
Indicates the relationship between an earthquake event and the total energy it releases, quantified as its seismic moment.
-
D.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
E.
secondaryIsland
Indicates that one island is a secondary or subordinate island in relation to a primary or main island.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf40f7908190a450c3136fccb020 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.