Triple
T5458759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream Chaser spaceplane |
E122543
|
entity |
| Predicate | takeoffMode |
P14512
|
FINISHED |
| Object | launched on a rocket |
—
|
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: launched on a rocket | Statement: [Dream Chaser spaceplane, takeoffMode, launched on a rocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffMode Context triple: [Dream Chaser spaceplane, takeoffMode, launched on a rocket]
-
A.
takeoffMethod
chosen
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
-
B.
takeoffCharacteristic
Indicates the specific properties or conditions associated with how an entity takes off, such as its manner, performance, or requirements during takeoff.
-
C.
takeoffBase
Indicates the location or base from which a takeoff (such as of an aircraft or flight) originates.
-
D.
takeoffPower
Indicates the power level an aircraft or engine produces specifically during the takeoff phase of flight.
-
E.
takeoffDistanceCharacteristic
Indicates the relationship between an aircraft (or flight operation) and a characteristic describing the distance required or used for takeoff.
- 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_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. |
Created at: March 20, 2026, 2:08 p.m.