Triple

T35022959
Position Surface form Disambiguated ID Type / Status
Subject Syrian Coastal Mountain Range E1010244 entity
Predicate hasAverageElevationRange P122621 FINISHED
Object 500–1500 m 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: 500–1500 m | Statement: [Syrian Coastal Mountain Range, hasAverageElevationRange, 500–1500 m]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAverageElevationRange
Context triple: [Syrian Coastal Mountain Range, hasAverageElevationRange, 500–1500 m]
  • A. hasAverageElevation
    Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
  • B. typicalElevationRange
    Indicates the usual range of elevation values within which something commonly occurs or exists.
  • C. elevationCoverageApproximate
    Indicates an approximate or estimated representation of how elevation values are covered or distributed over a given area or dataset.
  • D. isHighElevation
    Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
  • E. altitudeRange_m chosen
    Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
  • 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_69f76dccf0108190af43b465d3750196 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7858aa5508190a07dde993b3356fc completed May 3, 2026, 5:27 p.m.
PD Predicate disambiguation batch_69f7841812f081909d878955d114088e completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.