Triple

T23971803
Position Surface form Disambiguated ID Type / Status
Subject Second Kaweah E604252 entity
Predicate hasHighElevation P73807 FINISHED
Object true 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: true | Statement: [Second Kaweah, hasHighElevation, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHighElevation
Context triple: [Second Kaweah, hasHighElevation, true]
  • A. isHighElevation chosen
    Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
  • B. hasElevationFeature
    Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
  • C. hasHigherElevationArea
    Indicates that one area is situated at a greater elevation above sea level than another area.
  • D. higherInlandElevation
    Indicates that one location has a greater elevation above sea level than another location, specifically when both are considered in an inland (away from the coast) context.
  • E. hasAverageElevation
    Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
  • 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_69e29543019c8190872462e593cc50b4 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d1dcef248190a04718f6f436dcc8 completed April 29, 2026, 9:39 a.m.
PD Predicate disambiguation batch_69f161578d54819084a8b35496299993 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:25 p.m.