Triple
T22999648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asellus Borealis |
E572600
|
entity |
| Predicate | hasDeclinationEpochJ2000 |
P66369
|
FINISHED |
| Object | +21° 28′ 07″ |
—
|
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: +21° 28′ 07″ | Statement: [Asellus Borealis, hasDeclinationEpochJ2000, +21° 28′ 07″]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeclinationEpochJ2000 Context triple: [Asellus Borealis, hasDeclinationEpochJ2000, +21° 28′ 07″]
-
A.
hasDeclinationJ2000
Indicates that an entity has an associated celestial declination coordinate specified in the J2000 reference frame.
-
B.
equatorialCoordinateEpoch
chosen
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
C.
approxDeclinationJ2000
Indicates an approximate value of an object's declination coordinate in the J2000.0 celestial reference frame.
-
D.
hasObliquityPeriod
Indicates the relationship between an object and the duration of its axial tilt (obliquity) cycle.
-
E.
declinationFrame
Indicates the reference frame or coordinate system in which a declination angle or value is defined.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.