Triple
T4267430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayward Fault |
E96858
|
entity |
| Predicate | observedPhenomenon |
P23475
|
FINISHED |
| Object | aseismic creep |
—
|
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: aseismic creep | Statement: [Hayward Fault, observedPhenomenon, aseismic creep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedPhenomenon Context triple: [Hayward Fault, observedPhenomenon, aseismic creep]
-
A.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
B.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
C.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
D.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
E.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.