Triple
T34028223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Piscis Austrini |
E872567
|
entity |
| Predicate | hasRingLikeDustBelt |
P27657
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alpha Piscis Austrini, hasRingLikeDustBelt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingLikeDustBelt Context triple: [Alpha Piscis Austrini, hasRingLikeDustBelt, true]
-
A.
hasRingSystem
Indicates that an entity possesses a ring-shaped structural system or configuration.
-
B.
hasDebrisDisk
chosen
Indicates that an astronomical object is surrounded by a disk of dust and debris, typically leftover from planet formation or collisions.
-
C.
hasRingSystemType
Indicates that an entity possesses a ring system and specifies the type or classification of that ring system.
-
D.
systemHasInnerAsteroidBelt
Indicates that a planetary system contains an asteroid belt located in its inner region, closer to the central star than any outer belts.
-
E.
hasExtendedDustyRegion
Indicates that an entity possesses a surrounding area or zone characterized by dust that extends outward beyond its immediate vicinity.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:51 a.m.