Triple
T36204443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Planetary Orbiter |
E1047352
|
entity |
| Predicate | plannedMissionPhase |
P184641
|
FINISHED |
| Object | Mercury orbit operations |
—
|
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: Mercury orbit operations | Statement: [Mercury Planetary Orbiter, plannedMissionPhase, Mercury orbit operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedMissionPhase Context triple: [Mercury Planetary Orbiter, plannedMissionPhase, Mercury orbit operations]
-
A.
missionProfilePhase
chosen
Indicates the specific phase or stage within a mission profile during which an action, condition, or relationship is applicable.
-
B.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
C.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
D.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
E.
coversMissionPhase
Indicates that one entity’s scope, responsibility, or applicability extends over a specified mission phase.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:08 p.m.