Triple
T8055270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suborbital Pad A |
E187982
|
entity |
| Predicate | hasLaunchMountType |
P34295
|
FINISHED |
| Object | suborbital launch mount |
—
|
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: suborbital launch mount | Statement: [Suborbital Pad A, hasLaunchMountType, suborbital launch mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchMountType Context triple: [Suborbital Pad A, hasLaunchMountType, suborbital launch mount]
-
A.
hasMountingFeature
chosen
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
B.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
C.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
D.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa16804819094926ff2ff053c80 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.