Triple
T15027719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler-452b |
E378259
|
entity |
| Predicate | exoplanetStatus |
P116443
|
FINISHED |
| Object | confirmed exoplanet |
—
|
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: confirmed exoplanet | Statement: [Kepler-452b, exoplanetStatus, confirmed exoplanet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exoplanetStatus Context triple: [Kepler-452b, exoplanetStatus, confirmed exoplanet]
-
A.
hasExoplanet
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
-
B.
hasExoplanetsDetected
Indicates that one or more exoplanets have been observed and confirmed to exist in association with the referenced astronomical object.
-
C.
planetarySystemStatus
Indicates the current condition or operational state of a planetary system, such as its stability, activity level, or lifecycle phase.
-
D.
hasNumberOfConfirmedPlanets
Indicates the relationship that specifies how many planets within a given system or context have been confirmed to exist.
-
E.
hasHabitableZonePlanetsStatus
Indicates whether a star system currently has one or more planets located within its habitable zone.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e0e8c88190ac6f5786b4d4040f |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:58 a.m.