Triple

T4618264
Position Surface form Disambiguated ID Type / Status
Subject Caloris Basin E100918 entity
Predicate hasCoordinateSystemReference P2054 FINISHED
Object Mercury planetocentric coordinates 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: Mercury planetocentric coordinates | Statement: [Caloris Basin, hasCoordinateSystemReference, Mercury planetocentric coordinates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCoordinateSystemReference
Context triple: [Caloris Basin, hasCoordinateSystemReference, Mercury planetocentric coordinates]
  • A. coordinateSystem chosen
    Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
  • B. hasSummitCoordinateSystem
    Indicates that a summit or peak is associated with a specific coordinate system used to define its geographic position.
  • C. isReferencePointFor
    Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
  • D. hasCoordinateRole
    Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
  • E. hasCoordinates
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • 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_69bd43cf363c819087fd5ab441b4a3f4 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd59e247448190ad92f194cb1127c5 completed March 20, 2026, 2:29 p.m.
PD Predicate disambiguation batch_69bd522fd5c48190ad2bffc0a5bc9061 completed March 20, 2026, 1:57 p.m.
Created at: March 20, 2026, 1:12 p.m.