Triple
T12681303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMOTENASHI CubeSat |
E302952
|
entity |
| Predicate | plannedLandingMode |
P12133
|
FINISHED |
| Object | semi-hard landing |
—
|
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: semi-hard landing | Statement: [OMOTENASHI CubeSat, plannedLandingMode, semi-hard landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLandingMode Context triple: [OMOTENASHI CubeSat, plannedLandingMode, semi-hard landing]
-
A.
plannedLandingMethod
chosen
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
B.
intendedLandingRegion
Indicates the geographic area or region where something is planned or expected to land.
-
C.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
D.
lastFlightPlannedLandingSite
Indicates the location where the most recent flight is scheduled to land.
-
E.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b32dbc81908101fc5f07e26ed3 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.