Triple

T19932196
Position Surface form Disambiguated ID Type / Status
Subject Alpha Ophiuchi E479081 entity
Predicate hasProjectedRotationalVelocity_kmPerS P137888 FINISHED
Object 240 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: 240 | Statement: [Alpha Ophiuchi, hasProjectedRotationalVelocity_kmPerS, 240]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProjectedRotationalVelocity_kmPerS
Context triple: [Alpha Ophiuchi, hasProjectedRotationalVelocity_kmPerS, 240]
  • A. hasRotationalVelocityKmPerSec
    Indicates that an entity possesses a rotational speed measured in kilometers per second.
  • B. hasRotationalVelocity
    Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
  • C. 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.
  • D. hasRotationCurve
    Indicates that an object is associated with a rotation curve describing how its rotational velocity varies with radius or position.
  • E. 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.
  • 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_69d8e521855c8190b41871700afc8d6a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65a14a2348190b41f8e320fe661d6 completed April 20, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69e537f070b481908958e0e5911dcdc1 completed April 19, 2026, 8:15 p.m.
PDg Predicate description generation batch_69e543c136b081909cab9394b958390a completed April 19, 2026, 9:06 p.m.
Created at: April 10, 2026, 1:53 p.m.