Triple
T37761219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581h |
E941276
|
entity |
| Predicate | planetaryStatus |
P116443
|
FINISHED |
| Object | retracted candidate |
—
|
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: retracted candidate | Statement: [Gliese 581h, planetaryStatus, retracted candidate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryStatus Context triple: [Gliese 581h, planetaryStatus, retracted candidate]
-
A.
planetStatus
Indicates the current condition or classification of a planet, such as its state, category, or operational status within a given context.
-
B.
planetarySystemStatus
Indicates the current condition or operational state of a planetary system, such as its stability, activity level, or lifecycle phase.
-
C.
exoplanetStatus
chosen
Indicates the classification or current condition of a planet located outside our solar system, such as whether it is confirmed, candidate, or unconfirmed as an exoplanet.
-
D.
isPlanet
Indicates that the subject entity is classified as a planet.
-
E.
inPlanet
Indicates that one entity is located within or on the planetary body of another entity.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef947488190837b9cc9d8c9bde9 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.