Triple
T34028097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fomalhaut |
E872564
|
entity |
| Predicate | hasStellarCompanion |
P84325
|
FINISHED |
| Object | TW Piscis Austrini |
—
|
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: TW Piscis Austrini | Statement: [Fomalhaut, hasStellarCompanion, TW Piscis Austrini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarCompanion Context triple: [Fomalhaut, hasStellarCompanion, TW Piscis Austrini]
-
A.
hasCompanionStar
chosen
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
B.
hasPulsarCompanion
Indicates that one astronomical object exists in a bound system with, or is accompanied by, a pulsar.
-
C.
hasOpticalCompanion
Indicates that one entity has another entity as an associated optical companion, typically observed as a nearby or paired object in optical wavelengths.
-
D.
hasSiblingStars
Indicates that two or more stars share at least one common parent system or origin, making them siblings in an astrophysical or formation context.
-
E.
hasStarSystem
Indicates that an entity possesses, contains, or is associated with a particular star system.
- 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_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 1, 2026, 1:51 a.m.