Triple
T1565637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Crew Program |
E33425
|
entity |
| Predicate | requiresCapability |
P29514
|
FINISHED |
| Object | launch abort system |
—
|
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: launch abort system | Statement: [Commercial Crew Program, requiresCapability, launch abort system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCapability Context triple: [Commercial Crew Program, requiresCapability, launch abort system]
-
A.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
B.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
C.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
D.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
E.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a90fcb8ca48190a9ee50559ba73b22 |
completed | March 5, 2026, 5:08 a.m. |
Created at: March 4, 2026, 7:27 p.m.