Triple
T16691048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASPERA-3 |
E405592
|
entity |
| Predicate | planetaryMissionType |
P124264
|
FINISHED |
| Object | Mars orbiter mission instrument |
—
|
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: Mars orbiter mission instrument | Statement: [ASPERA-3, planetaryMissionType, Mars orbiter mission instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryMissionType Context triple: [ASPERA-3, planetaryMissionType, Mars orbiter mission instrument]
-
A.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
B.
missionTypeForCassini–Huygens
Indicates the type or category of space mission associated with the Cassini–Huygens spacecraft.
-
C.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
D.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
E.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or operation.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea99bac8190a6c559ed7b7d8ecd |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:19 a.m.