Triple

T2202483
Position Surface form Disambiguated ID Type / Status
Subject Astana E50521 entity
Predicate elevationAboveSeaLevel_m P221 FINISHED
Object 347 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: 347 | Statement: [Astana, elevationAboveSeaLevel_m, 347]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: elevationAboveSeaLevel_m
Context triple: [Astana, elevationAboveSeaLevel_m, 347]
  • A. elevation chosen
    Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
  • B. highestElevationApprox
    Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
  • C. hasAverageElevation
    Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
  • D. elevationBy
    Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
  • E. highestPoint
    Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
  • 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_69a88b044ab48190add007487680f009 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfa33f0881908403604eafb73ecf completed March 7, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69abbda706f4819094de73e1d1d1f539 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.