Triple

T26410866
Position Surface form Disambiguated ID Type / Status
Subject Linosa Trough E663955 entity
Predicate tectonicFeature P35761 FINISHED
Object rift-related basin 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: rift-related basin | Statement: [Linosa Trough, tectonicFeature, rift-related basin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tectonicFeature
Context triple: [Linosa Trough, tectonicFeature, rift-related basin]
  • A. isTectonicFeature
    Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
  • B. tectonicFeaturesPresence
    Indicates the existence or occurrence of tectonic features (such as faults, folds, or plate boundaries) in a specified area or context.
  • C. isPartOfTectonicFeature
    Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
  • D. hasTypeOfTectonicFeature chosen
    Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
  • E. tectonicActivityCharacteristic
    Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
  • 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_69ee883931888190901be96d75ee23cc completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6113143f481909c64dfc1975e3a59 completed May 2, 2026, 2:58 p.m.
PD Predicate disambiguation batch_69f5f800fa9c8190aab0962669fde8ac completed May 2, 2026, 1:11 p.m.
Created at: April 26, 2026, 11:38 p.m.