Triple

T19831645
Position Surface form Disambiguated ID Type / Status
Subject W3(OH) E476473 entity
Predicate hasProperMotionMeasurements P133143 FINISHED
Object yes 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: yes | Statement: [W3(OH), hasProperMotionMeasurements, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProperMotionMeasurements
Context triple: [W3(OH), hasProperMotionMeasurements, yes]
  • A. hasProperMotionMeasurement chosen
    Indicates that a proper motion value (the apparent angular movement across the sky over time) has been measured and recorded for the entity.
  • B. properMotionMeasuredBy
    Indicates that the proper motion of an astronomical object has been determined using a specific instrument, survey, or observational method.
  • 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.

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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e656ce68b48190aa25b29d0b6ea021 completed April 20, 2026, 4:39 p.m.
PD Predicate disambiguation batch_69e5305bda388190a23b7191768107b1 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:50 p.m.