Triple
T32449136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encke Gap |
E829229
|
entity |
| Predicate | hasMeanRadiusFromSaturn |
P197332
|
FINISHED |
| Object | approximately 133,600 kilometers |
—
|
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: approximately 133,600 kilometers | Statement: [Encke Gap, hasMeanRadiusFromSaturn, approximately 133,600 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanRadiusFromSaturn Context triple: [Encke Gap, hasMeanRadiusFromSaturn, approximately 133,600 kilometers]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
relativeSizeInSaturnSystem
Indicates the comparative size relationship of an object relative to other objects within the Saturn system.
-
C.
relativeSizeToMimasRadius
Indicates the size of an object expressed as a ratio or multiple of the radius of Mimas.
-
D.
hasRingSystem
Indicates that an entity possesses a ring-shaped structural system or configuration.
-
E.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
- F. None of above. chosen
Provenance (4 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: May 1, 2026, 12:56 a.m.