Triple
T35086862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun |
E1012599
|
entity |
| Predicate | heliosphereExtent |
P126832
|
FINISHED |
| Object | extends beyond Pluto |
—
|
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: extends beyond Pluto | Statement: [Sun, heliosphereExtent, extends beyond Pluto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heliosphereExtent Context triple: [Sun, heliosphereExtent, extends beyond Pluto]
-
A.
hasHeliosphere
Indicates that an object possesses a surrounding region of space dominated by its own stellar wind and magnetic field, known as a heliosphere.
-
B.
heliocentricDistance_kpc
Indicates the distance of an object from the Sun, measured in kiloparsecs.
-
C.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
-
D.
maximumElongationFromSun
Indicates the greatest angular separation an object can have from the Sun as seen by an observer, typically measured in degrees along the sky.
-
E.
cosmicBoundary
chosen
Indicates a relationship where something marks, defines, or lies at the outermost limit or edge of a cosmic region, domain, or structure.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.