Triple

T19366833
Position Surface form Disambiguated ID Type / Status
Subject Daedalia Planum E484423 entity
Predicate hasRemoteSensingData P135663 FINISHED
Object visible imagery 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: visible imagery | Statement: [Daedalia Planum, hasRemoteSensingData, visible imagery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRemoteSensingData
Context triple: [Daedalia Planum, hasRemoteSensingData, visible imagery]
  • A. hasRemoteSensingDataFrom
    Indicates that one entity possesses or is associated with remote sensing data that was obtained from another entity or source.
  • B. hasSpatialResolution
    Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
  • C. hasSolarRadiation
    Indicates that an entity is subject to, receives, or is characterized by a certain amount or presence of solar radiation.
  • D. hasImageryFrom
    Indicates that one entity contains, incorporates, or is derived from the imagery produced or provided by another entity.
  • E. hasColorImagery
    Indicates that something includes or is characterized by visual elements emphasizing specific colors or color-based symbolism.
  • F. None of above. chosen

Provenance (4 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619ac26d4819095836d737b629cf1 completed April 20, 2026, 12:18 p.m.
PD Predicate disambiguation batch_69e4fd54f8e48190956e73dd8969164a completed April 19, 2026, 4:05 p.m.
PDg Predicate description generation batch_69e5004c23308190a087b7941a90725f completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 1:35 p.m.