Triple
T18458190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 90377 Sedna |
E450958
|
entity |
| Predicate | aphelionRegion |
P97654
|
FINISHED |
| Object | inner Oort cloud candidate region |
—
|
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: inner Oort cloud candidate region | Statement: [90377 Sedna, aphelionRegion, inner Oort cloud candidate region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aphelionRegion Context triple: [90377 Sedna, aphelionRegion, inner Oort cloud candidate region]
-
A.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
B.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
C.
apoapsisType
chosen
Indicates the specific kind or classification of an orbit’s apoapsis (farthest point from the central body) associated with an entity.
-
D.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
E.
targetRegionOnMars
Indicates that an entity designates or is associated with a specific geographic region located on the planet Mars.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.