Triple
T15881168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energetic Particles Detector |
E385076
|
entity |
| Predicate | orbitsObservedFrom |
P120886
|
FINISHED |
| Object | Jupiter orbit |
—
|
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: Jupiter orbit | Statement: [Energetic Particles Detector, orbitsObservedFrom, Jupiter orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsObservedFrom Context triple: [Energetic Particles Detector, orbitsObservedFrom, Jupiter orbit]
-
A.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
B.
spacecraftTypeObservedFrom
Indicates that a particular type of spacecraft was observed from a specified vantage point or observing platform.
-
C.
orbitsEarth
Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
-
D.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
-
E.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.