Triple
T25637976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metis |
E642757
|
entity |
| Predicate | distanceFromJupiterCloudTops_km |
P115203
|
FINISHED |
| Object | ~1000 above main ring plane |
—
|
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: ~1000 above main ring plane | Statement: [Metis, distanceFromJupiterCloudTops_km, ~1000 above main ring plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromJupiterCloudTops_km Context triple: [Metis, distanceFromJupiterCloudTops_km, ~1000 above main ring plane]
-
A.
distanceFromSaturnCloudTops
Indicates the measured or specified distance between an entity and the tops of Saturn’s cloud layer.
-
B.
distanceFromNeptuneCloudTop
Indicates the measured separation between an object and the top boundary of Neptune’s cloud layer.
-
C.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
-
D.
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.
-
E.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 21, 2026, 5:36 p.m.