Triple
T23244372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 1411 |
E581541
|
entity |
| Predicate | hasRightAscensionEpoch |
P66369
|
FINISHED |
| Object | J2000 |
—
|
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: J2000 | Statement: [HR 1411, hasRightAscensionEpoch, J2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightAscensionEpoch Context triple: [HR 1411, hasRightAscensionEpoch, J2000]
-
A.
equatorialCoordinateEpoch
chosen
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
B.
hasRightAscensionConstellation
Indicates that an astronomical object’s right ascension places it within a specific constellation.
-
C.
hasDeclinationJ2000
Indicates that an entity has an associated celestial declination coordinate specified in the J2000 reference frame.
-
D.
rightAscensionRange
Indicates that an entity’s right ascension lies within a specified angular interval on the celestial sphere.
-
E.
rightAscensionConstellation
Indicates that an entity’s right ascension position on the celestial sphere is associated with a specific constellation.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.