Triple
T34933307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Landers earthquake |
E1007500
|
entity |
| Predicate | ruptureDirection |
P161020
|
FINISHED |
| Object | north-northwest |
—
|
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: north-northwest | Statement: [1992 Landers earthquake, ruptureDirection, north-northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruptureDirection Context triple: [1992 Landers earthquake, ruptureDirection, north-northwest]
-
A.
ruptureConsequence
Indicates the resulting state, effect, or outcome that follows from a rupture event.
-
B.
rupturesDuring
Indicates that one event or process ruptures or breaks while another specified event or time period is occurring.
-
C.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
-
D.
rupturedSegmentOf
Indicates that one entity is a segment that has undergone rupture and is part of, or derived from, another entity.
-
E.
breakDirection
chosen
Indicates the direction in which something breaks, splits, or fractures relative to a reference point or orientation.
- 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_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.