Triple
T32731339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denali Fault |
E836962
|
entity |
| Predicate | ruptureLength2002Event |
P54664
|
FINISHED |
| Object | hundreds of kilometers |
—
|
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: hundreds of kilometers | Statement: [Denali Fault, ruptureLength2002Event, hundreds of kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruptureLength2002Event Context triple: [Denali Fault, ruptureLength2002Event, hundreds of kilometers]
-
A.
seismicRuptureLength
chosen
Indicates the length of the fault segment that ruptures during a seismic event.
-
B.
ruptureEventsFrequency
Indicates how often rupture events occur within a given time or context.
-
C.
surfaceRupture
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
-
D.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
E.
seismicEvent
Indicates the occurrence of a naturally or artificially induced ground-shaking event, such as an earthquake or tremor, at a specific place and time.
- 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_69f6c8cd5cd48190b4d44faed8fcce07 |
completed | May 3, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.