Triple
T21326887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4459 |
E525781
|
entity |
| Predicate | hasDustDisk |
P137492
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NGC 4459, hasDustDisk, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDustDisk Context triple: [NGC 4459, hasDustDisk, yes]
-
A.
hasDebrisDisk
Indicates that an astronomical object is surrounded by a disk of dust and debris, typically leftover from planet formation or collisions.
-
B.
hasCircumstellarDisks
chosen
Indicates that the subject celestial object possesses one or more disks of gas and/or dust surrounding it in the region around the star.
-
C.
hasDustDiskOrientation
Indicates the spatial orientation or alignment of an object's surrounding dust disk relative to a reference frame or observer.
-
D.
hasExtendedDustyRegion
Indicates that an entity possesses a surrounding area or zone characterized by dust that extends outward beyond its immediate vicinity.
-
E.
debrisDiskType
Indicates the specific classification or subtype of a debris disk associated with an astronomical object.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab4a796081908148ec9106362d3d |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:41 p.m.