Triple

T27085361
Position Surface form Disambiguated ID Type / Status
Subject Crimean seismic zone E686021 entity
Predicate hasSeismicGap P188767 FINISHED
Object local segments with lower recent activity 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: local segments with lower recent activity | Statement: [Crimean seismic zone, hasSeismicGap, local segments with lower recent activity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSeismicGap
Context triple: [Crimean seismic zone, hasSeismicGap, local segments with lower recent activity]
  • A. hasSeismicBehavior
    Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
  • B. hasLastMajorSurfaceRuptureIn
    Indicates that an entity experienced its most recent significant surface-rupturing event within a specified time or temporal interval.
  • C. hasEarthquakes
    Indicates that the specified location or region experiences one or more earthquakes.
  • D. hasEstimatedMagnitude
    Indicates that an entity is associated with an approximate or calculated value representing its magnitude or size.
  • E. hasAvalancheRisk
    Indicates that there is a potential or assessed danger of an avalanche occurring in relation to the referenced entity.
  • F. None of above. chosen

Provenance (4 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_69ef148940ec819097b5c20fbfbf7c81 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
PDg Predicate description generation batch_69fbad1b3ba08190ad69e21461333f2e completed May 6, 2026, 9:05 p.m.
Created at: April 27, 2026, 8:37 a.m.