Triple

T35979656
Position Surface form Disambiguated ID Type / Status
Subject Tuz Gölü Basin E1040526 entity
Predicate tectonicControl P63844 FINISHED
Object fault-bounded 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: fault-bounded basin | Statement: [Tuz Gölü Basin, tectonicControl, fault-bounded basin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tectonicControl
Context triple: [Tuz Gölü Basin, tectonicControl, fault-bounded basin]
  • A. tectonicFunction
    Indicates the role or effect that an entity has in tectonic processes, such as influencing plate movements, deformation, or related geodynamic activity.
  • B. hasTectonicSetting
    Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
  • C. tectonicImportance
    Indicates the degree to which something plays a significant role or has notable influence in tectonic processes or tectonic activity.
  • D. isTectonicFeature
    Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
  • E. tectonicFeaturesPresence chosen
    Indicates the existence or occurrence of tectonic features (such as faults, folds, or plate boundaries) in a specified area or context.
  • 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_69f76e28293c8190ae3f4e2208b87117 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7acaec1508190a38f2ac9cc5383e7 completed May 3, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69f7ab75387c819091afc3c2128eb903 completed May 3, 2026, 8:09 p.m.
Created at: May 3, 2026, 4:07 p.m.