Triple
T25638369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euanthe |
E642767
|
entity |
| Predicate | orbitalSense |
P7214
|
FINISHED |
| Object | retrograde with respect to Jupiter’s rotation |
—
|
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: retrograde with respect to Jupiter’s rotation | Statement: [Euanthe, orbitalSense, retrograde with respect to Jupiter’s rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalSense Context triple: [Euanthe, orbitalSense, retrograde with respect to Jupiter’s rotation]
-
A.
orbitalDetectionBy
Indicates that an orbital object or phenomenon is detected, observed, or measured by a specified instrument, sensor, or detection system.
-
B.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
C.
orbitsEarth
Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
-
D.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
E.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 5:37 p.m.