Triple

T4078560
Position Surface form Disambiguated ID Type / Status
Subject South Sandwich Island Arc E87422 entity
Predicate subductionZoneType P7367 FINISHED
Object intra-oceanic subduction zone 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: intra-oceanic subduction zone | Statement: [South Sandwich Island Arc, subductionZoneType, intra-oceanic subduction zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subductionZoneType
Context triple: [South Sandwich Island Arc, subductionZoneType, intra-oceanic subduction zone]
  • A. subductionZoneName
    Indicates the specific name assigned to a subduction zone where one tectonic plate is forced beneath another.
  • B. subductionStyle chosen
    Indicates the manner or mode in which one tectonic plate descends beneath another at a convergent plate boundary.
  • C. crustTypeSubducting
    Indicates that one type of crust is moving beneath another plate in a subduction process.
  • D. affectsSubductionZone
    Indicates that one entity has an influence or impact on the behavior, characteristics, or dynamics of a subduction zone.
  • E. hasSubductingPlate
    Indicates that one tectonic plate is moving beneath and being forced under another plate at a convergent plate boundary.
  • 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_69aed9435cf48190ad1da737c962d19d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc4e95b08190bd1ee8f6d3a9613c completed March 9, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69aef9082c2081908474f082a49bebc8 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:39 p.m.