Triple
T24722197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 8 |
E612335
|
entity |
| Predicate | landingStatus |
P86470
|
FINISHED |
| Object | unsuccessful |
—
|
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: unsuccessful | Statement: [Luna 8, landingStatus, unsuccessful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingStatus Context triple: [Luna 8, landingStatus, unsuccessful]
-
A.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
B.
landedStatus
chosen
Indicates the current landing-related state or outcome of an entity, such as whether it has successfully landed, is in the process of landing, or has failed to land.
-
C.
landingAttemptResult
Indicates the outcome or status of an attempted landing action, such as whether the landing succeeded, failed, or had another specific result.
-
D.
landingOperation
Indicates an operation in which an aircraft, spacecraft, or similar vehicle descends and makes contact with a surface to complete its landing.
-
E.
landingPilot
Indicates that an entity is acting as the pilot responsible for landing an aircraft or spacecraft.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:41 a.m.