Triple
T34933265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerson fault |
E1007499
|
entity |
| Predicate | surfaceRuptureObserved |
P106756
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Emerson fault, surfaceRuptureObserved, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceRuptureObserved Context triple: [Emerson fault, surfaceRuptureObserved, yes]
-
A.
surfaceRupture
chosen
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
-
B.
rupturedFaultSystem
Indicates that a seismic event has caused a fault system to break and slip along one or more of its segments.
-
C.
hasLastMajorSurfaceRuptureIn
Indicates that an entity experienced its most recent significant surface-rupturing event within a specified time or temporal interval.
-
D.
earthquakeFault
Indicates that one entity is a geological fault associated with, or responsible for, the occurrence of an earthquake affecting the other entity.
-
E.
seismicRuptureLength
Indicates the length of the fault segment that ruptures during a 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.