Triple
T4140025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno |
E89248
|
entity |
| Predicate | periapsisDistanceFromJupiterCloudTops |
P13780
|
FINISHED |
| Object | about 4200 km |
—
|
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: about 4200 km | Statement: [Juno, periapsisDistanceFromJupiterCloudTops, about 4200 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periapsisDistanceFromJupiterCloudTops Context triple: [Juno, periapsisDistanceFromJupiterCloudTops, about 4200 km]
-
A.
closestApproachDistanceToJupiter
chosen
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
-
B.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
-
C.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
-
D.
massInJupiterOrbit
Indicates the mass an object has while it is located in orbit around Jupiter.
-
E.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.