Triple
T28067303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship spacecraft |
E709289
|
entity |
| Predicate | firstFlightVehicleVariant |
P103741
|
FINISHED |
| Object | Starship SN8 |
—
|
NE NERFINISHED |
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: Starship SN8 | Statement: [Starship spacecraft, firstFlightVehicleVariant, Starship SN8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightVehicleVariant Context triple: [Starship spacecraft, firstFlightVehicleVariant, Starship SN8]
-
A.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
B.
firstModelToFly
Indicates that the subject is the earliest or original model among a set that successfully achieved flight.
-
C.
firstAircraftName
Indicates the name assigned to the first aircraft associated with a given entity or context.
-
D.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
E.
firstSuccessfulFlightDesignation
chosen
Indicates the specific designation or identifier assigned to an aircraft or spacecraft for its first successful flight.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 27, 2026, 8:43 p.m.