Triple
T23185886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 61 Cygni |
E579591
|
entity |
| Predicate | hasHighProperMotion |
P151273
|
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: [61 Cygni, hasHighProperMotion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighProperMotion Context triple: [61 Cygni, hasHighProperMotion, true]
-
A.
hasProperMotionMeasurement
Indicates that a proper motion value (the apparent angular movement across the sky over time) has been measured and recorded for the entity.
-
B.
highProperMotionNotedBy
Indicates that an observer or source has recorded that an object exhibits unusually large or significant proper motion across the sky.
-
C.
properMotion
Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
-
D.
properMotionDec
Indicates the rate of change of an object's position over time in the declination (north–south) direction on the celestial sphere.
-
E.
properMotionRA_masPerYear
Indicates the rate of change in an object's right ascension position on the sky, measured in milliarcseconds per year.
- F. None of above. chosen
Provenance (4 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f7230208190820acf52f537b3ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:05 p.m.