Triple

T4271254
Position Surface form Disambiguated ID Type / Status
Subject Otero County, New Mexico E96944 entity
Predicate containsDuneField P10619 FINISHED
Object gypsum sand dunes of White Sands 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: gypsum sand dunes of White Sands | Statement: [Otero County, New Mexico, containsDuneField, gypsum sand dunes of White Sands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsDuneField
Context triple: [Otero County, New Mexico, containsDuneField, gypsum sand dunes of White Sands]
  • A. hasDuneType
    Indicates that one entity is characterized by or associated with a specific type or classification of dune.
  • B. hasDunes chosen
    Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
  • C. hasFieldDivision
    Indicates that one entity is organizationally divided into, or associated with, a specific field-based subdivision of another entity.
  • D. fieldPresenceIn
    Indicates that something exists or is located within a particular field, area, or domain.
  • E. notableDune
    Indicates that something is a particularly significant or well-known sand dune, distinguished from ordinary dunes by its prominence, uniqueness, or recognition.
  • 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ffb85a88190af000b94673bff59 completed March 12, 2026, 11:44 p.m.
PD Predicate disambiguation batch_69b347faa45481908c19c29fb906dc92 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:07 p.m.