Triple
T4118008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceShipOne |
E90339
|
entity |
| Predicate | reentryTechnique |
P30129
|
FINISHED |
| Object | feathered reentry |
—
|
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: feathered reentry | Statement: [SpaceShipOne, reentryTechnique, feathered reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryTechnique Context triple: [SpaceShipOne, reentryTechnique, feathered reentry]
-
A.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
B.
reentryProfile
chosen
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
C.
reentryVehicle
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
D.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
E.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.