Triple

T19685930
Position Surface form Disambiguated ID Type / Status
Subject Sculptor Group E472710 entity
Predicate radialVelocityRange P64733 FINISHED
Object roughly 150–500 km/s 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: roughly 150–500 km/s | Statement: [Sculptor Group, radialVelocityRange, roughly 150–500 km/s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: radialVelocityRange
Context triple: [Sculptor Group, radialVelocityRange, roughly 150–500 km/s]
  • A. hasRadialVelocity_km_per_s chosen
    Indicates that one entity has a measured radial velocity, expressed in kilometers per second, relative to another reference frame or object.
  • B. 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.
  • C. radialVelocityAmplitude
    Indicates the magnitude of variation in an object's radial (line-of-sight) velocity, typically representing the semi-amplitude of its periodic Doppler shift.
  • D. hasRadialVelocitySignature
    Indicates that an object exhibits a measurable radial velocity pattern characteristic of a specific physical process or source.
  • E. hasRadialVelocityDispersion
    Indicates that an entity exhibits a spread in its radial velocities, quantifying how much the line-of-sight speeds of its components differ from one another.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e641c33b94819081bdeb56910f6ff8 completed April 20, 2026, 3:09 p.m.
PD Predicate disambiguation batch_69e53039ea808190a9106a53f564ab92 completed April 19, 2026, 7:42 p.m.
Created at: April 10, 2026, 1:45 p.m.