Triple
T35498808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do 335 A-1 |
E1025939
|
entity |
| Predicate | crewEscapeSystem |
P24229
|
FINISHED |
| Object | ejection seat |
—
|
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: ejection seat | Statement: [Do 335 A-1, crewEscapeSystem, ejection seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewEscapeSystem Context triple: [Do 335 A-1, crewEscapeSystem, ejection seat]
-
A.
crewLaunchEscapeSystem
Indicates that a crewed spacecraft is equipped with or uses a launch escape system designed to rapidly carry the crew module away from a failing launch vehicle.
-
B.
crewEscapeCapability
chosen
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
C.
launchEscapeSystem
Indicates initiating or activating an emergency mechanism designed to rapidly propel occupants or payload away from a vehicle or structure to ensure their safety.
-
D.
launcherTubes
Indicates that one entity serves as or contains the launcher tubes associated with another entity.
-
E.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.