Triple

T14037853
Position Surface form Disambiguated ID Type / Status
Subject Lomonosov (lunar crater) E337759 entity
Predicate isInvisibleFrom P95706 FINISHED
Object Earth-based optical telescopes 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: Earth-based optical telescopes | Statement: [Lomonosov (lunar crater), isInvisibleFrom, Earth-based optical telescopes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInvisibleFrom
Context triple: [Lomonosov (lunar crater), isInvisibleFrom, Earth-based optical telescopes]
  • A. hidesFrom
    Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
  • B. isPartiallyVisibleFrom
    Indicates that one entity can be seen only in part, rather than fully, from the viewpoint or location of another entity.
  • C. visibleAt
    Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
  • D. notVisibleWhen chosen
    Indicates that one entity is not visible whenever a specified condition, state, or context involving another entity holds.
  • E. isViewableIn
    Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de30e312148190a6be0a3258364e6e completed April 14, 2026, 12:19 p.m.
PD Predicate disambiguation batch_69de05ab36b48190920efb1869bdb1fe completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:20 p.m.