Triple

T29308474
Position Surface form Disambiguated ID Type / Status
Subject Himachal Himalaya E743164 entity
Predicate highestPeaksType P18615 FINISHED
Object high Himalayan peaks 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 Himalayan peaks | Statement: [Himachal Himalaya, highestPeaksType, high Himalayan peaks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: highestPeaksType
Context triple: [Himachal Himalaya, highestPeaksType, high Himalayan peaks]
  • A. highestPeaksLocatedIn
    Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
  • B. hasHighestPointType chosen
    Indicates that the highest point of an entity is of a specified type or category.
  • C. highestPeakAccessible
    Indicates that one location is the tallest peak that can be reached or accessed from another specified location or by a specified agent.
  • D. peakOf
    Indicates that one entity represents the highest or most extreme point, level, or intensity within the extent or progression of another entity.
  • E. highestPeaksRelativeTo
    Indicates a relationship where one location or region is associated with the tallest mountain peaks it contains, relative to surrounding areas or a defined reference set.
  • 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_69f09123ed9881909f351f7541933f5e completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: April 28, 2026, 1:15 p.m.