Triple
T12639348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars 3 |
E301850
|
entity |
| Predicate | communicationAfterLanding |
P106141
|
FINISHED |
| Object | lost shortly after touchdown |
—
|
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: lost shortly after touchdown | Statement: [Mars 3, communicationAfterLanding, lost shortly after touchdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationAfterLanding Context triple: [Mars 3, communicationAfterLanding, lost shortly after touchdown]
-
A.
landingRecovery
Indicates the process or method by which something is retrieved or secured after it has landed.
-
B.
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.
-
C.
crewLandingStatus
Indicates the status or outcome of a crew’s landing event, such as whether and how the crew has successfully landed.
-
D.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
E.
landingOperation
Indicates an operation in which an aircraft, spacecraft, or similar vehicle descends and makes contact with a surface to complete 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
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:16 p.m.