Triple

T18956617
Position Surface form Disambiguated ID Type / Status
Subject Santa Maria Rupes E463795 entity
Predicate isTectonicFeature P133949 FINISHED
Object true 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: true | Statement: [Santa Maria Rupes, isTectonicFeature, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTectonicFeature
Context triple: [Santa Maria Rupes, isTectonicFeature, true]
  • A. isPartOfTectonicFeature
    Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
  • B. hasTypeOfTectonicFeature
    Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
  • C. isFedByTectonicPlate
    Indicates that something (such as a geological feature or process) receives material, energy, or influence from the movement or interaction of a specific tectonic plate.
  • D. tectonicFeaturesPresence
    Indicates the existence or occurrence of tectonic features (such as faults, folds, or plate boundaries) in a specified area or context.
  • E. hasTectonicSetting
    Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
  • F. None of above. chosen

Provenance (4 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5cdf2d08190a0aecd3fa5335a75 completed April 20, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69e4a2f437648190b85650dae8885d48 completed April 19, 2026, 9:40 a.m.
PDg Predicate description generation batch_69e4ad8e075c8190ad561edc5e520057 completed April 19, 2026, 10:25 a.m.
Created at: April 10, 2026, noon