Triple
T29918209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridgecrest fault system |
E759848
|
entity |
| Predicate | faultStyle |
P3827
|
FINISHED |
| Object | right-lateral strike-slip |
—
|
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: right-lateral strike-slip | Statement: [Ridgecrest fault system, faultStyle, right-lateral strike-slip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultStyle Context triple: [Ridgecrest fault system, faultStyle, right-lateral strike-slip]
-
A.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
B.
typeOfFaulting
chosen
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
C.
throwsStyle
Indicates that one entity performs a throwing action using a particular style, technique, or manner.
-
D.
strainType
Indicates the specific variety or subtype classification within a broader category of strains (e.g., biological, chemical, or product strains).
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6779140408190987216918cfaf0cb |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:13 p.m.