Triple

T697736
Position Surface form Disambiguated ID Type / Status
Subject Mount Kosciuszko E13928 entity
Predicate hasSummitInfrastructure P8666 FINISHED
Object summit cairn 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: summit cairn | Statement: [Mount Kosciuszko, hasSummitInfrastructure, summit cairn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSummitInfrastructure
Context triple: [Mount Kosciuszko, hasSummitInfrastructure, summit cairn]
  • A. hasSummitFeature chosen
    Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
  • B. hasSummit
    Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
  • C. hasSummitCoordinates
    Indicates that an entity has specific geographic coordinates identifying the location of its summit.
  • D. summitAffected
    Indicates that a summit, meeting, or high-level event has been influenced, impacted, or altered by a specified factor or circumstance.
  • E. hasMountain
    Indicates that a location or region possesses or contains at least one mountain.
  • 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_69a493406c408190957eeec9048a8fb6 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a0c99be48190babc37c397b6a186 completed March 1, 2026, 8:25 p.m.
PD Predicate disambiguation batch_69a49d2586b081908e052cc5ba1d2685 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.