Triple

T32731338
Position Surface form Disambiguated ID Type / Status
Subject Denali Fault E836962 entity
Predicate maximumObservedEarthquakeMagnitude P163908 FINISHED
Object approximately 7.9 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: approximately 7.9 | Statement: [Denali Fault, maximumObservedEarthquakeMagnitude, approximately 7.9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumObservedEarthquakeMagnitude
Context triple: [Denali Fault, maximumObservedEarthquakeMagnitude, approximately 7.9]
  • A. earthquakeMagnitude
    Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
  • B. largestRecordedEarthquake chosen
    Indicates that the related entity experienced the most powerful earthquake ever recorded for its category or region.
  • C. largestAftershockMagnitude
    Indicates the magnitude value of the largest aftershock that occurs following a primary seismic event.
  • D. limitingMagnitude
    Indicates the faintest detectable level or threshold of an effect, signal, or quantity beyond which it can no longer be reliably observed or measured.
  • E. notableAftershockMagnitude
    Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic event.
  • 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_69f34935fb048190ad4967420581f835 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fb563aec448190875410fb1a3ed624 completed May 6, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69fb35b9ede881908aaae93a215525df completed May 6, 2026, 12:36 p.m.
Created at: May 1, 2026, 1:11 a.m.