Triple

T35676392
Position Surface form Disambiguated ID Type / Status
Subject Vega E1030871 entity
Predicate projectedRotationalVelocity_km_s P137888 FINISHED
Object ~274 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: ~274 | Statement: [Vega, projectedRotationalVelocity_km_s, ~274]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: projectedRotationalVelocity_km_s
Context triple: [Vega, projectedRotationalVelocity_km_s, ~274]
  • A. hasProjectedRotationalVelocity_kmPerS chosen
    Indicates the rotational speed an object appears to have along our line of sight, measured in kilometers per second.
  • B. hasRotationalVelocityKmPerSec
    Indicates that an entity possesses a rotational speed measured in kilometers per second.
  • C. hasRadialVelocity_km_per_s
    Indicates that one entity has a measured radial velocity, expressed in kilometers per second, relative to another reference frame or object.
  • D. radialVelocityRelativeToMilkyWay
    Indicates the speed and direction at which an object is moving toward or away from the Milky Way galaxy along the line of sight.
  • E. hasRadialVelocityMeasurement
    Indicates that a radial velocity value has been measured for an entity, typically quantifying its motion along the line of sight relative to an observer.
  • 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_69f76e0acfc0819082c8495c2210ce73 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79fe647f081908e651c61ba350ba8 completed May 3, 2026, 7:20 p.m.
PD Predicate disambiguation batch_69f79e4d885881908a3612e2e75cf84f completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.