Triple

T3283980
Position Surface form Disambiguated ID Type / Status
Subject Sovanco Fracture Zone E68936 entity
Predicate tectonicRegion P944 FINISHED
Object Cascadia subduction system vicinity 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: Cascadia subduction system vicinity | Statement: [Sovanco Fracture Zone, tectonicRegion, Cascadia subduction system vicinity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tectonicRegion
Context triple: [Sovanco Fracture Zone, tectonicRegion, Cascadia subduction system vicinity]
  • A. locatedOnTectonicPlate
    Indicates that one entity (typically a geographic region or feature) lies upon or is situated on the tectonic plate represented by the other entity.
  • B. naturalRegionType
    Indicates the type or category of natural region to which a given area or place belongs.
  • C. planetRegion
    Indicates that a specified region or area is located on or associated with a particular planet.
  • D. stratotypeRegion
    Indicates the region or geographic area that serves as the reference or standard location (stratotype) for a particular stratigraphic unit or interval.
  • E. locatedOnTectonicBoundary chosen
    Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another 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_69ad859c463481909ca4be267336c290 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb03621608190a2b7a6b38d6559da completed March 8, 2026, 5:21 p.m.
PD Predicate disambiguation batch_69ada421fadc8190b7c7d3c8afd20061 completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:10 p.m.