Triple

T34708750
Position Surface form Disambiguated ID Type / Status
Subject Arabia–India–Somalia triple-plate region E1000577 entity
Predicate hasGeodynamicSetting P17577 FINISHED
Object oceanic triple junction 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: oceanic triple junction | Statement: [Arabia–India–Somalia triple-plate region, hasGeodynamicSetting, oceanic triple junction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeodynamicSetting
Context triple: [Arabia–India–Somalia triple-plate region, hasGeodynamicSetting, oceanic triple junction]
  • A. hasTectonicSetting chosen
    Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
  • B. seismicSetting
    Indicates the geological or tectonic conditions under which seismic activity occurs or is characterized.
  • C. hasGeologicalNature
    Indicates that something possesses a specific geological character, composition, or formation type.
  • D. hasSeismicBehavior
    Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
  • E. hasGeosphere
    Indicates that an entity possesses or includes a solid rocky component of a planetary body (its geosphere).
  • 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_69f76dab937881909c86f1b9ad50445f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: May 3, 2026, 3:59 p.m.