Triple
T25638024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrastea |
E642758
|
entity |
| Predicate | isCloserToJupiterThan |
P115203
|
FINISHED |
| Object | Amalthea |
—
|
NE NERFINISHED |
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: Amalthea | Statement: [Adrastea, isCloserToJupiterThan, Amalthea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCloserToJupiterThan Context triple: [Adrastea, isCloserToJupiterThan, Amalthea]
-
A.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
-
B.
relationToJupiter
chosen
Indicates a spatial or conceptual relationship that an entity has with the planet Jupiter, such as position, distance, or association relative to it.
-
C.
isOuterSolarSystemObject
Indicates that an astronomical object resides in the outer regions of a solar system, beyond the orbit of the major inner planets.
-
D.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
E.
closestApproachDistanceToJupiter
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
- 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_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:36 p.m.