Triple
T34028206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Piscis Austrini |
E872567
|
entity |
| Predicate | exoplanetDetectionMethod |
P27665
|
FINISHED |
| Object | direct imaging |
—
|
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: direct imaging | Statement: [Alpha Piscis Austrini, exoplanetDetectionMethod, direct imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exoplanetDetectionMethod Context triple: [Alpha Piscis Austrini, exoplanetDetectionMethod, direct imaging]
-
A.
planetDetectionMethod
chosen
Indicates the method or technique by which a planet was discovered or detected.
-
B.
hasExoplanetsDetected
Indicates that one or more exoplanets have been observed and confirmed to exist in association with the referenced astronomical object.
-
C.
debrisDiskDiscoveryMethod
Indicates the method or technique used to discover or detect a debris disk around an astronomical object.
-
D.
hasExoplanets
Indicates that the subject celestial system or star possesses one or more confirmed exoplanets in orbit around it.
-
E.
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.
- 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_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:51 a.m.