Triple

T4765013
Position Surface form Disambiguated ID Type / Status
Subject Skolio E105786 entity
Predicate relativeHeightRankOnMountOlympus P39147 FINISHED
Object second-highest peak 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: second-highest peak | Statement: [Skolio, relativeHeightRankOnMountOlympus, second-highest peak]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeHeightRankOnMountOlympus
Context triple: [Skolio, relativeHeightRankOnMountOlympus, second-highest peak]
  • A. rankOnMountAthos
    Indicates the hierarchical or positional rank that an entity holds within the monastic or administrative structure on Mount Athos.
  • B. summitElevationRank chosen
    Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
  • C. relativeToMountEverest
    Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
  • D. positionRelativeToSummit
    Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
  • E. rankByHeightWorld
    Indicates an ordering of entities based on their relative height compared to all others in the world.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:21 p.m.