Triple
T4018007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Express |
E91209
|
entity |
| Predicate | Beagle2Status |
P53468
|
FINISHED |
| Object | lost on Mars surface after landing attempt |
—
|
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 on Mars surface after landing attempt | Statement: [Mars Express, Beagle2Status, lost on Mars surface after landing attempt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Beagle2Status Context triple: [Mars Express, Beagle2Status, lost on Mars surface after landing attempt]
-
A.
orbiterStatus
Indicates the current operational or mission state of an orbiting spacecraft relative to its target body or mission phase.
-
B.
roverName
Indicates that an entity is the name assigned to a particular rover.
-
C.
previousMissionOfOrbiter
Indicates that one mission is the immediately preceding mission undertaken by a given orbiter.
-
D.
usedLunarRovingVehicle
Indicates that an entity operated or traveled using a lunar roving vehicle during a lunar mission or activity.
-
E.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa984948190a252eaeb9dbae454 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:35 p.m.