Triple
T15716556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler-186f |
E380974
|
entity |
| Predicate | hostStarRadiusRelativeToSun |
P57022
|
FINISHED |
| Object | about 0.52 solar 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 0.52 solar radii | Statement: [Kepler-186f, hostStarRadiusRelativeToSun, about 0.52 solar radii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStarRadiusRelativeToSun Context triple: [Kepler-186f, hostStarRadiusRelativeToSun, about 0.52 solar radii]
-
A.
hasRadius_solarRadius
chosen
Indicates that an entity has a radius whose value is expressed in units of the Sun’s radius.
-
B.
relativeSizeInSaturnSystem
Indicates the comparative size relationship of an object relative to other objects within the Saturn system.
-
C.
luminosityRelativeToSun
Indicates how bright an object is compared to the Sun, expressed as a ratio of their luminosities.
-
D.
hostStarRotation
Indicates the rotational motion or spin characteristics of a host star in relation to its planetary system or orbiting bodies.
-
E.
declinationOfHostStar
Indicates the angular distance of the host star north or south of the celestial equator, defining its declination on the sky.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f91beb08190bd91bf9306737c3b |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.