Triple
T29323081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP Aerospace |
E743563
|
entity |
| Predicate | operatesInOrbitRegime |
P48448
|
FINISHED |
| Object | suborbital |
—
|
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 | Statement: [UP Aerospace, operatesInOrbitRegime, suborbital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInOrbitRegime Context triple: [UP Aerospace, operatesInOrbitRegime, suborbital]
-
A.
designedForOrbitType
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
B.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
D.
supportsOrbitRegimes
chosen
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
-
E.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 28, 2026, 1:24 p.m.