Triple

T33081060
Position Surface form Disambiguated ID Type / Status
Subject Orion EFT-1 E846507 entity
Predicate testedScenario P144932 FINISHED
Object lunar-return-like reentry conditions 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: lunar-return-like reentry conditions | Statement: [Orion EFT-1, testedScenario, lunar-return-like reentry conditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: testedScenario
Context triple: [Orion EFT-1, testedScenario, lunar-return-like reentry conditions]
  • A. testedInCase
    Indicates that something (such as a method, component, or behavior) is exercised or verified within a particular test case.
  • B. testedUnder chosen
    Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
  • C. testedFor
    Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
  • D. testedProcess
    Indicates that an entity has performed a test or evaluation on a specific process.
  • E. testedConfiguration
    Indicates that a particular configuration has been examined or validated through testing in relation to another entity or context.
  • 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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6a6b04c8190bee4cf9c00665ef7 completed May 3, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69f6d27120988190aacec621cf2bf0e8 completed May 3, 2026, 4:43 a.m.
Created at: May 1, 2026, 1:26 a.m.