Triple
T7353025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europa Clipper mission |
E169550
|
entity |
| Predicate | plannedArrivalAtJupiterSystem |
P54105
|
FINISHED |
| Object | 2030 |
—
|
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: 2030 | Statement: [Europa Clipper mission, plannedArrivalAtJupiterSystem, 2030]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedArrivalAtJupiterSystem Context triple: [Europa Clipper mission, plannedArrivalAtJupiterSystem, 2030]
-
A.
arrivalAtJupiter
chosen
Indicates the event or state of something reaching and arriving at Jupiter as its destination.
-
B.
JupiterOrbitInsertionDate
Indicates the date on which a spacecraft successfully enters orbit around Jupiter.
-
C.
closestApproachToJupiterDate
Indicates the date on which an object reaches its minimum distance from Jupiter during its trajectory or orbit.
-
D.
arrivalAtMarsDate
Indicates the specific date on which an entity arrives at Mars.
-
E.
JupiterAtmosphericProbeEntryDate
Indicates the date on which an atmospheric probe enters the atmosphere of Jupiter.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.