Triple
T156281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solar System |
E3187
|
entity |
| Predicate | hasHeliosphere |
P7298
|
FINISHED |
| Object | heliosphere |
—
|
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: heliosphere | Statement: [Solar System, hasHeliosphere, heliosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeliosphere Context triple: [Solar System, hasHeliosphere, heliosphere]
-
A.
hasMagnetosphere
Indicates that an astronomical body possesses a magnetic field strong enough to create a surrounding magnetosphere.
-
B.
hasNaturalSatellite
Indicates that one celestial body is orbited by another body that occurs naturally as its satellite.
-
C.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
D.
hasEventHorizon
Indicates that an object possesses an event horizon, a boundary beyond which events cannot affect an outside observer.
-
E.
hasEscapeVelocity
Indicates that an object or body possesses a velocity sufficient to overcome the gravitational pull of another body without further propulsion.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587e598c81909e1082b813971f48 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.