Triple
T15716564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler-186f |
E380974
|
entity |
| Predicate | directImagingStatus |
P20816
|
FINISHED |
| Object | not directly imaged |
—
|
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: not directly imaged | Statement: [Kepler-186f, directImagingStatus, not directly imaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directImagingStatus Context triple: [Kepler-186f, directImagingStatus, not directly imaged]
-
A.
observationalStatus
chosen
Indicates the current state or condition of an observation, such as whether it has been made, recorded, verified, or remains pending.
-
B.
IAUStatus
Indicates the formal classification or recognition status of an astronomical object or entity as defined by the International Astronomical Union (IAU).
-
C.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
D.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
E.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
- 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.