Triple

T4885579
Position Surface form Disambiguated ID Type / Status
Subject Valles Marineris E109430 entity
Predicate formedPrimarilyBy P972 FINISHED
Object tectonic extension 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: tectonic extension | Statement: [Valles Marineris, formedPrimarilyBy, tectonic extension]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formedPrimarilyBy
Context triple: [Valles Marineris, formedPrimarilyBy, tectonic extension]
  • A. primarilyFor
    Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
  • B. formedBy chosen
    Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
  • C. usedPrimarilyIn
    Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
  • D. primaryInfluence
    Indicates that one entity serves as the main or most significant influencing factor on another entity’s state, behavior, or outcome.
  • E. performsPrimarilyIn
    Indicates that an entity (such as a performer or group) mainly carries out its performances within a particular location, medium, 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_69bd440f71348190b99938e59fb7f9a1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6de3718881908521968fa6e6b444 completed March 20, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69bd6c2be5e881909f6ec9c3bcde49f3 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:27 p.m.