Triple

T430452
Position Surface form Disambiguated ID Type / Status
Subject Romanche Fracture Zone E9699 entity
Predicate seafloorFeatureType P4263 FINISHED
Object deep-sea fracture 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: deep-sea fracture zone | Statement: [Romanche Fracture Zone, seafloorFeatureType, deep-sea fracture zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seafloorFeatureType
Context triple: [Romanche Fracture Zone, seafloorFeatureType, deep-sea fracture zone]
  • A. seafloorType chosen
    Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
  • B. geologicalFormation
    Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
  • C. basinType
    Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
  • D. tectonicActivityCharacteristic
    Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
  • E. oceanBasin
    Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
  • 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eeef065c81908ed30528a61da132 completed Feb. 28, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69a2edd9264c8190b92f9a50348e5541 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.