Triple
T20612697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wezen |
E506485
|
entity |
| Predicate | hasProperMotion_Dec_mas_per_yr |
P24835
|
FINISHED |
| Object | +4 |
—
|
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: +4 | Statement: [Wezen, hasProperMotion_Dec_mas_per_yr, +4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperMotion_Dec_mas_per_yr Context triple: [Wezen, hasProperMotion_Dec_mas_per_yr, +4]
-
A.
properMotionRA_masPerYear
Indicates the rate of change in an object's right ascension position on the sky, measured in milliarcseconds per year.
-
B.
hasProperMotionMeasurement
Indicates that a proper motion value (the apparent angular movement across the sky over time) has been measured and recorded for the entity.
-
C.
properMotionDec_mas_yr
chosen
Indicates the rate of change in an object's position on the sky in the declination direction, measured in milliarcseconds per year.
-
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.
meanProperMotionUncertainty
Indicates the uncertainty associated with the measured mean proper motion of an 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.