Triple

T31487915
Position Surface form Disambiguated ID Type / Status
Subject Oaxacan Complex of Mexico E803327 entity
Predicate tectonicUnitType P171693 FINISHED
Object basement terrane 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: basement terrane | Statement: [Oaxacan Complex of Mexico, tectonicUnitType, basement terrane]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tectonicUnitType
Context triple: [Oaxacan Complex of Mexico, tectonicUnitType, basement terrane]
  • A. geologicUnitOf
    Indicates that one entity is a geologic unit to which the other entity belongs or with which it is associated.
  • 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. lithosphereType
    Indicates the classification of a lithospheric unit according to its type (e.g., oceanic, continental, or other defined categories).
  • D. geologicType
    Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
  • E. hasTectonicAffinity
    Indicates a relationship where one geological unit or feature shares a common tectonic origin, setting, or structural association with another.
  • 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_69f348ca04508190ba9379b5329dfd75 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a1b60e5481909b64fde96bc5c64a completed May 3, 2026, 1:15 a.m.
PD Predicate disambiguation batch_69f69fe82e5c81909da9db0a2f3bba6d completed May 3, 2026, 1:07 a.m.
PDg Predicate description generation batch_69f6a0e920cc8190a943fdd0594906c5 completed May 3, 2026, 1:12 a.m.
Created at: April 30, 2026, 9:36 p.m.