Triple
T5458796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream Chaser spaceplane |
E122543
|
entity |
| Predicate | crewLifeSupportCapability |
P64179
|
FINISHED |
| Object | planned for crewed variant |
—
|
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: planned for crewed variant | Statement: [Dream Chaser spaceplane, crewLifeSupportCapability, planned for crewed variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLifeSupportCapability Context triple: [Dream Chaser spaceplane, crewLifeSupportCapability, planned for crewed variant]
-
A.
crewEscapeCapability
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
B.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
C.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
D.
intendedCrewVehicle
Indicates that a particular vehicle is designated or planned to be used by a specific crew.
-
E.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd927b0b4c81909d5e0f594822e3f9 |
completed | March 20, 2026, 6:31 p.m. |
Created at: March 20, 2026, 2:08 p.m.