Triple
T30397153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendale Fault |
E773248
|
entity |
| Predicate | associatedEarthquakeMagnitude |
P5297
|
FINISHED |
| Object | moment magnitude 7.1 |
—
|
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: moment magnitude 7.1 | Statement: [Greendale Fault, associatedEarthquakeMagnitude, moment magnitude 7.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEarthquakeMagnitude Context triple: [Greendale Fault, associatedEarthquakeMagnitude, moment magnitude 7.1]
-
A.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
earthquakeMagnitudeRange
Indicates the range of magnitudes within which an earthquake’s measured strength falls.
-
C.
largestAftershockMagnitude
Indicates the magnitude value of the largest aftershock that occurs following a primary seismic event.
-
D.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
-
E.
largestRecordedEarthquake
Indicates that the related entity experienced the most powerful earthquake ever recorded for its category or 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:03 p.m.