Triple
T464411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship launch system |
E8413
|
entity |
| Predicate | launchConfiguration |
P8441
|
FINISHED |
| Object | two-stage-to-orbit |
—
|
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: two-stage-to-orbit | Statement: [Starship launch system, launchConfiguration, two-stage-to-orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchConfiguration Context triple: [Starship launch system, launchConfiguration, two-stage-to-orbit]
-
A.
launchProfile
chosen
Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
-
B.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
C.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
D.
launchPad
Indicates a physical platform or site from which vehicles, typically rockets or spacecraft, are launched.
-
E.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd5b6b48190ae23968135cf6417 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.