Triple
T15881236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jovian ring system |
E385078
|
entity |
| Predicate | outerBoundaryApproximateRadius |
P67815
|
FINISHED |
| Object | about 3.5 Jupiter radii |
—
|
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 3.5 Jupiter radii | Statement: [Jovian ring system, outerBoundaryApproximateRadius, about 3.5 Jupiter radii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerBoundaryApproximateRadius Context triple: [Jovian ring system, outerBoundaryApproximateRadius, about 3.5 Jupiter radii]
-
A.
hasOuterBoundaryRadius
chosen
Indicates that an entity has an outer boundary characterized by a specific radius measurement.
-
B.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
C.
radialExtent
Indicates the radial distance or range over which something extends outward from a central point or axis.
-
D.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
E.
curveRadius
Indicates the radius of curvature associated with an object or path, describing how sharply it bends at a given point.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.