Triple

T25858563
Position Surface form Disambiguated ID Type / Status
Subject Limagne fault E651417 entity
Predicate orogenyRelatedTo P54598 FINISHED
Object Alpine orogeny NE NERFINISHED

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: Alpine orogeny | Statement: [Limagne fault, orogenyRelatedTo, Alpine orogeny]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orogenyRelatedTo
Context triple: [Limagne fault, orogenyRelatedTo, Alpine orogeny]
  • A. orogenAssociatedWith chosen
    Indicates an association between a geological feature or process and a specific orogen (mountain-building event or belt), without specifying the exact nature of that association.
  • B. orogeny
    Indicates the geological process by which mountain ranges are formed, typically through tectonic plate interactions such as collision, subduction, or compression.
  • C. orogenyIncludes
    Indicates that a particular orogenic (mountain-building) event encompasses or contains another geological feature, phase, or process as part of it.
  • D. orogenType
    Indicates the type or classification of orogeny (mountain-building event) associated with a geological feature or region.
  • E. involvedInOrogeny
    Indicates involvement in the geological mountain-building process of an orogeny, either as a contributing factor or as a participant in its formation.
  • 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_69e7ab3a199c81909227cb964cacfe24 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f60269c0fc8190a73fa347f8d99281 completed May 2, 2026, 1:55 p.m.
PD Predicate disambiguation batch_69f4939148dc81908706cec7d85291bc completed May 1, 2026, 11:50 a.m.
Created at: April 22, 2026, 8:04 a.m.