Triple

T23244016
Position Surface form Disambiguated ID Type / Status
Subject local standard of rest E581533 entity
Predicate hasVelocityComponent P151502 FINISHED
Object U (toward Galactic center) 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: U (toward Galactic center) | Statement: [local standard of rest, hasVelocityComponent, U (toward Galactic center)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVelocityComponent
Context triple: [local standard of rest, hasVelocityComponent, U (toward Galactic center)]
  • A. hasTypicalVelocity
    Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
  • B. hasRotationalVelocity
    Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
  • C. hasEscapeVelocity
    Indicates that an object or body possesses a velocity sufficient to overcome the gravitational pull of another body without further propulsion.
  • D. hasVerticalMotion
    Indicates that an entity is undergoing or exhibiting motion in the vertical direction (upward or downward).
  • E. hasPropulsionComponent
    Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
  • 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_69e24606b17c81908aba1a4911c8a8ba completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f192efd44c8190b179b4d1cb71efa5 completed April 29, 2026, 5:11 a.m.
PD Predicate disambiguation batch_69effcdadec0819092ec1749ee453b4e completed April 28, 2026, 12:18 a.m.
PDg Predicate description generation batch_69f01d8770d081908897c28b04e5faea completed April 28, 2026, 2:37 a.m.
Created at: April 17, 2026, 4:10 p.m.