Triple
T2855535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jacinto Fault Zone |
E63190
|
entity |
| Predicate | maximumMagnitudeEstimate |
P5297
|
FINISHED |
| Object | around magnitude 7.5 |
—
|
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: around magnitude 7.5 | Statement: [San Jacinto Fault Zone, maximumMagnitudeEstimate, around magnitude 7.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumMagnitudeEstimate Context triple: [San Jacinto Fault Zone, maximumMagnitudeEstimate, around magnitude 7.5]
-
A.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
C.
maximumIntensity
Indicates the greatest level or strength that a quantity, effect, or signal can reach within a given context.
-
D.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
E.
seismicMoment
Indicates the relationship between an earthquake event and the total energy it releases, quantified as its seismic moment.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf62308081908a65decdd5d6f918 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.