Triple
T395496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 2 |
E8973
|
entity |
| Predicate | missionPhase |
P8100
|
FINISHED |
| Object | interstellar mission |
—
|
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: interstellar mission | Statement: [Voyager 2, missionPhase, interstellar mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPhase Context triple: [Voyager 2, missionPhase, interstellar mission]
-
A.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
B.
currentMissionPhase
chosen
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
C.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
D.
majorCapturePhase
Indicates a significant or primary stage in a capture process where the main act of seizing, acquiring, or taking control occurs.
-
E.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec792dd081909b6b18a854139f8c |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.