Triple
T34028095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fomalhaut |
E872564
|
entity |
| Predicate | exoplanetCandidate |
P69237
|
FINISHED |
| Object | Fomalhaut b |
—
|
NE NERFINISHED |
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: Fomalhaut b | Statement: [Fomalhaut, exoplanetCandidate, Fomalhaut b]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exoplanetCandidate Context triple: [Fomalhaut, exoplanetCandidate, Fomalhaut b]
-
A.
exoplanetStatus
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.
-
B.
hasCandidateExoplanets
Indicates that an astronomical object or system is associated with one or more potential exoplanets that meet specified candidacy criteria.
-
C.
isAmongClosestKnownExoplanetCandidates
Indicates that an exoplanet candidate is one of the nearest such candidates to Earth currently identified.
-
D.
isExoplanetSearchTarget
Indicates that an astronomical object has been identified as a suitable target for searching for exoplanets.
-
E.
hasExoplanet
chosen
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.