Triple

T26798431
Position Surface form Disambiguated ID Type / Status
Subject Sand Mountain Field E671029 entity
Predicate alignmentControl P161490 FINISHED
Object regional tectonic fractures 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: regional tectonic fractures | Statement: [Sand Mountain Field, alignmentControl, regional tectonic fractures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alignmentControl
Context triple: [Sand Mountain Field, alignmentControl, regional tectonic fractures]
  • A. alignmentShape
    Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
  • B. alignmentGoal
    Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
  • C. alignmentChange
    Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
  • D. alignmentComponents
    Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
  • E. alignmentConcept
    Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
  • 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_69eeb31fbd888190a82dac5822e453bc completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f619c30bf8819080d159c49e525a2d completed May 2, 2026, 3:35 p.m.
PD Predicate disambiguation batch_69f611ad2eb48190ac1ed0090f13f7a9 completed May 2, 2026, 3:01 p.m.
PDg Predicate description generation batch_69f6142a0b988190b404d078f73c3cb9 completed May 2, 2026, 3:11 p.m.
Created at: April 27, 2026, 4:21 a.m.