Triple
T21123463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno |
E520490
|
entity |
| Predicate | enteredJupiterOrbit |
P54105
|
FINISHED |
| Object | 2016-07-05 UTC |
—
|
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: 2016-07-05 UTC | Statement: [Juno, enteredJupiterOrbit, 2016-07-05 UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredJupiterOrbit Context triple: [Juno, enteredJupiterOrbit, 2016-07-05 UTC]
-
A.
enteredHeliocentricOrbit
Indicates that an object has moved into and is now traveling in an orbit around the Sun as its central body.
-
B.
enteredKuiperBelt
Indicates that an object has crossed into and is now within the region of space defined as the Kuiper Belt.
-
C.
arrivalAtJupiter
chosen
Indicates the event or state of something reaching and arriving at Jupiter as its destination.
-
D.
enteredMercuryOrbitDate
Indicates the date on which a spacecraft or object successfully entered into orbit around the planet Mercury.
-
E.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.