Triple
T1236489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldebaran |
E26559
|
entity |
| Predicate | properMotionRA |
P6962
|
FINISHED |
| Object | +62.78 mas/yr |
—
|
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: +62.78 mas/yr | Statement: [Aldebaran, properMotionRA, +62.78 mas/yr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: properMotionRA Context triple: [Aldebaran, properMotionRA, +62.78 mas/yr]
-
A.
properMotion
chosen
Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
-
B.
positionRelativeToGalacticCenter
Indicates the spatial location of an entity expressed in relation to the center of its galaxy.
-
C.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
-
D.
rightAscension
Indicates the angular distance of an object measured eastward along the celestial equator from the vernal equinox, specifying its position in the sky.
-
E.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf17e0bc8190a066561e6b629fc0 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.