Triple

T21112308
Position Surface form Disambiguated ID Type / Status
Subject Mare Insularum E520202 entity
Predicate hasEjectaOverlay P49676 FINISHED
Object Copernicus crater ejecta 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: Copernicus crater ejecta | Statement: [Mare Insularum, hasEjectaOverlay, Copernicus crater ejecta]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEjectaOverlay
Context triple: [Mare Insularum, hasEjectaOverlay, Copernicus crater ejecta]
  • A. hasEjecta chosen
    Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
  • B. canEject
    Indicates that one entity has the ability or permission to forcibly remove or expel another entity from a place, system, or context.
  • C. hasCoverType
    Indicates that one entity possesses or is associated with a specific type or category of cover.
  • D. hasVignette
    Indicates that one entity possesses, includes, or is associated with a vignette (such as a brief scene, illustration, or decorative element).
  • E. hasCoverFeature
    Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
  • 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_69e0b509a318819092fbbcb21d1fe603 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72102d99c8190a1ea5a6981da6da0 completed April 21, 2026, 7:02 a.m.
PD Predicate disambiguation batch_69e5dbff56848190a03b350a9305c612 completed April 20, 2026, 7:55 a.m.
Created at: April 16, 2026, 2:54 p.m.