Triple

T32366793
Position Surface form Disambiguated ID Type / Status
Subject Amundsen crater E827015 entity
Predicate hasRimType P116877 FINISHED
Object worn and eroded rim 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: worn and eroded rim | Statement: [Amundsen crater, hasRimType, worn and eroded rim]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRimType
Context triple: [Amundsen crater, hasRimType, worn and eroded rim]
  • A. hasRim
    Indicates that one entity possesses or is equipped with a rim as a defining part or feature.
  • B. hasRimCharacteristic chosen
    Indicates that an entity possesses a specific feature, quality, or attribute related to its rim.
  • C. hasRimDiameter
    Indicates that one entity has a rim whose diameter is measured by or corresponds to the value or object represented by the other entity.
  • D. hasRoadAlongRim
    Indicates that a road runs adjacent to and follows the contour of a rim or edge of a geographic feature.
  • E. namedOnRim
    Indicates that an entity is named or inscribed specifically on the rim or edge of another object.
  • 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_69f349166d548190887b412fe908e2f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7b0e5744c8190a22c1e1d6fcfa466 completed May 3, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f7ab70d034819080295628497d8582 completed May 3, 2026, 8:09 p.m.
Created at: May 1, 2026, 12:50 a.m.