Triple
T15637674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler-22b |
E375986
|
entity |
| Predicate | isInKeplerFieldOfView |
P119561
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kepler-22b, isInKeplerFieldOfView, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInKeplerFieldOfView Context triple: [Kepler-22b, isInKeplerFieldOfView, yes]
-
A.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
-
B.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
C.
isAstronomicalObject
Indicates that something is classified as an astronomical object, such as a star, planet, moon, asteroid, or similar celestial body.
-
D.
hasEclipticProximity
Indicates that one celestial object lies close to another in terms of angular separation along or near the ecliptic plane.
-
E.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.