Triple
T38152880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRS-16 |
E952801
|
entity |
| Predicate | launchOrbitRegime |
P171533
|
FINISHED |
| Object | Low Earth 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: Low Earth orbit | Statement: [CRS-16, launchOrbitRegime, Low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchOrbitRegime Context triple: [CRS-16, launchOrbitRegime, Low Earth orbit]
-
A.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
-
B.
deploymentOrbit
chosen
Indicates the orbital path or trajectory into which an object (typically a spacecraft or satellite) is placed at the time of its deployment.
-
C.
relaunchOrbit
Indicates that an entity is placed back into orbit after having previously left or ceased its orbital path.
-
D.
supportsOrbitRegimes
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
-
E.
launchVehicleRole
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:21 p.m.