Triple
T34933354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Landers earthquake |
E1007500
|
entity |
| Predicate | JoshuaTreeMagnitude |
P5297
|
FINISHED |
| Object | 6.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: 6.1 | Statement: [1992 Landers earthquake, JoshuaTreeMagnitude, 6.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JoshuaTreeMagnitude Context triple: [1992 Landers earthquake, JoshuaTreeMagnitude, 6.1]
-
A.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
exampleMagnitude
Indicates a relationship where one entity serves as a representative or typical instance that illustrates the scale, size, or intensity (magnitude) of another entity or quantity.
-
C.
hasEstimatedMagnitude
Indicates that an entity is associated with an approximate or calculated value representing its magnitude or size.
-
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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.