Triple
T20814183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Martin X-33 |
E512390
|
entity |
| Predicate | intendedLaunchMode |
P140445
|
FINISHED |
| Object | single-stage-to-orbit concept validation |
—
|
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: single-stage-to-orbit concept validation | Statement: [Lockheed Martin X-33, intendedLaunchMode, single-stage-to-orbit concept validation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedLaunchMode Context triple: [Lockheed Martin X-33, intendedLaunchMode, single-stage-to-orbit concept validation]
-
A.
launchMode
Indicates the manner or configuration in which something is initiated or started, such as a process, application, or operation.
-
B.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
C.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
-
D.
intendedPerformanceMode
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
-
E.
plannedMode
chosen
Indicates that a particular mode, method, or state has been intentionally selected or scheduled in advance for use.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d4e43c8190aecce82a3f7e2de0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.