Triple
T12681304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMOTENASHI CubeSat |
E302952
|
entity |
| Predicate | plannedLandingSiteType |
P106258
|
FINISHED |
| Object | lunar near side |
—
|
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: lunar near side | Statement: [OMOTENASHI CubeSat, plannedLandingSiteType, lunar near side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLandingSiteType Context triple: [OMOTENASHI CubeSat, plannedLandingSiteType, lunar near side]
-
A.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
B.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
C.
hasMainLandingSite
Indicates that an entity has a primary or principal location where it arrives, lands, or makes contact.
-
D.
lastMissionLandingPlannedDate
Indicates the scheduled calendar date on which the final mission in a series is planned to land.
-
E.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:21 p.m.