Triple

T35391000
Position Surface form Disambiguated ID Type / Status
Subject Johnson Valley fault E1022936 entity
Predicate displacementDirection P3149 FINISHED
Object right-lateral along strike 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 along strike | Statement: [Johnson Valley fault, displacementDirection, right-lateral along strike]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: displacementDirection
Context triple: [Johnson Valley fault, displacementDirection, right-lateral along strike]
  • A. displacement chosen
    Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
  • B. displacementOption
    Indicates an available way or method by which something or someone can be moved, relocated, or shifted from one position or state to another.
  • C. displacementRate
    Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
  • D. dispersionDirection
    Indicates the direction in which something spreads, scatters, or disperses from its source.
  • E. intendedDisplacement
    Indicates that an action or event is meant to cause a change in position or location of an entity, regardless of whether that movement actually occurs.
  • 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_69f76df34ba48190bd80f0814cdcd540 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f794fc5e088190949c1dfddbbb33b6 completed May 3, 2026, 6:33 p.m.
PD Predicate disambiguation batch_69f7910770108190bdd39ddb5d304f54 completed May 3, 2026, 6:16 p.m.
Created at: May 3, 2026, 4:03 p.m.