Triple

T29767980
Position Surface form Disambiguated ID Type / Status
Subject Main Central Thrust E753966 entity
Predicate lithologyAbove P167859 FINISHED
Object high‑grade gneisses and schists 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: high‑grade gneisses and schists | Statement: [Main Central Thrust, lithologyAbove, high‑grade gneisses and schists]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lithologyAbove
Context triple: [Main Central Thrust, lithologyAbove, high‑grade gneisses and schists]
  • A. lithology
    Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
  • B. lithologyAffected
    Indicates that one lithology is influenced, altered, or impacted in some way by another geological process, material, or condition.
  • C. lithostratigraphicType
    Indicates the specific lithostratigraphic classification or unit type that characterizes a rock body or stratigraphic unit within a geological framework.
  • D. lithologyVariation
    Indicates variation in the rock or sediment type present within a geological unit or between compared geological units.
  • E. lithologyInFootwall
    Indicates that a specified lithology occurs within the footwall block relative to a fault or structural discontinuity.
  • 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_69f0ef827ff88190ade56e0b0846b713 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f6745f8354819085a81de5c32dd49e completed May 2, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69f66ac1a4fc81909740d2e52fbe6970 completed May 2, 2026, 9:21 p.m.
PDg Predicate description generation batch_69f66c59de9881909ebbb7b0ae7ab495 completed May 2, 2026, 9:27 p.m.
Created at: April 28, 2026, 8:39 p.m.