Triple

T25638762
Position Surface form Disambiguated ID Type / Status
Subject Sponde E642776 entity
Predicate distanceFromJupiterRange P115203 FINISHED
Object about 22 to 25 million km (Pasiphae group range) 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 22 to 25 million km (Pasiphae group range) | Statement: [Sponde, distanceFromJupiterRange, about 22 to 25 million km (Pasiphae group range)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromJupiterRange
Context triple: [Sponde, distanceFromJupiterRange, about 22 to 25 million km (Pasiphae group range)]
  • A. hasMeanDistanceFromJupiter
    Indicates that one entity has a specified average distance from the planet Jupiter.
  • B. closestApproachDistanceToJupiter
    Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
  • C. 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.
  • D. radiusRelativeToJupiter
    Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
  • E. distanceFromPluto
    Indicates the measured or calculated spatial distance between a given entity and the celestial body Pluto.
  • 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_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c475c58c8190a883554231e88c88 completed May 3, 2026, 9:56 p.m.
Created at: April 21, 2026, 5:38 p.m.