Triple

T14937960
Position Surface form Disambiguated ID Type / Status
Subject Anjar E372444 entity
Predicate isInSeismicZone P38434 FINISHED
Object earthquake-prone region of Kutch 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: earthquake-prone region of Kutch | Statement: [Anjar, isInSeismicZone, earthquake-prone region of Kutch]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInSeismicZone
Context triple: [Anjar, isInSeismicZone, earthquake-prone region of Kutch]
  • A. hasSeismicBehavior
    Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
  • B. geologicalHazardZoneFor
    Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
  • C. earthquakeHazardLevel
    Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
  • D. relatedEarthquakeZone chosen
    Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
  • E. earthquakeResistance
    Indicates how well an entity can withstand or remain functional during an earthquake without significant damage.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded64904d88190b6b4140da8e8199d completed April 15, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69de9a588c2c8190b1245a1c406f447c completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:38 a.m.