Triple
T70717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1989 Loma Prieta earthquake |
E1415
|
entity |
| Predicate | magnitudeMoment |
P1937
|
FINISHED |
| Object | 6.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: 6.9 | Statement: [1989 Loma Prieta earthquake, magnitudeMoment, 6.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnitudeMoment Context triple: [1989 Loma Prieta earthquake, magnitudeMoment, 6.9]
-
A.
magnitude
chosen
Indicates a relationship where a quantitative size, extent, or intensity is assigned to or compared between entities or values.
-
B.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
C.
epicenter
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
-
D.
radiusOfSevereDestruction
Indicates the distance from a central point within which damage or destruction is expected to be extremely severe.
-
E.
percentageOfWorldEarthquakes
Indicates the proportion of all earthquakes worldwide that occur in or are attributed to a specific entity 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eaa0df88190add55579b2b9fd02 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.