Triple

T37720426
Position Surface form Disambiguated ID Type / Status
Subject Crew Dragon In-Flight Abort Test E939567 entity
Predicate testCondition P29885 FINISHED
Object abort at maximum dynamic pressure 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: abort at maximum dynamic pressure | Statement: [Crew Dragon In-Flight Abort Test, testCondition, abort at maximum dynamic pressure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: testCondition
Context triple: [Crew Dragon In-Flight Abort Test, testCondition, abort at maximum dynamic pressure]
  • A. canCondition
    Indicates that one entity has the capability or potential to impose, apply, or bring about a particular condition on another entity or situation.
  • B. triggerCondition chosen
    Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
  • C. hasCondition
    Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
  • D. containsCondition
    Indicates that one entity includes, embodies, or is associated with a particular condition.
  • E. variableCondition
    Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
  • 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_69f76edc208c8190bc8b9683f75e1024 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaef0cec881908c2742d77d145901 completed May 6, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69fbadf632ec8190b14991c971258307 completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:18 p.m.