Triple

T9538046
Position Surface form Disambiguated ID Type / Status
Subject Shuttle Imaging Radar-B E230069 entity
Predicate repeatPassCapability P89686 FINISHED
Object yes 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: yes | Statement: [Shuttle Imaging Radar-B, repeatPassCapability, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: repeatPassCapability
Context triple: [Shuttle Imaging Radar-B, repeatPassCapability, yes]
  • A. hasRetakePolicy
    Indicates that there is a defined policy governing whether and how something (such as an exam, course, or assessment) may be taken again after an initial attempt.
  • B. repetitionOf
    Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
  • C. hasPass
    Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
  • D. usesRepetition
    Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
  • E. safeToRepeat
    Indicates that performing the same action or operation again under the current conditions is considered acceptable and will not cause harm or undesired effects.
  • 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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98cfead8819089a8f47ea83500a4 completed April 1, 2026, 10:14 p.m.
PD Predicate disambiguation batch_69ccd58bd21881908b860e3ee469af13 completed April 1, 2026, 8:21 a.m.
PDg Predicate description generation batch_69ccd93e90048190a2b0d7c5c195ba98 completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:01 p.m.