Triple

T5363418
Position Surface form Disambiguated ID Type / Status
Subject Nunki E103073 entity
Predicate rotationalVelocity_kmPerSec P21933 FINISHED
Object ~165 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: ~165 | Statement: [Nunki, rotationalVelocity_kmPerSec, ~165]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rotationalVelocity_kmPerSec
Context triple: [Nunki, rotationalVelocity_kmPerSec, ~165]
  • A. radialVelocityRelativeToM31
    Indicates the radial component of an object's velocity measured along the line of sight relative to the Andromeda Galaxy (M31), specifying how fast it is moving toward or away from M31.
  • B. velocityRelativeToSun
    Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
  • C. hasRadialVelocitySignature
    Indicates that an object exhibits a measurable radial velocity pattern characteristic of a specific physical process or source.
  • D. averageOrbitalSpeed
    Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
  • E. equatorialLinearSpeed chosen
    Indicates the linear (tangential) speed of a rotating body measured specifically at its equator.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd865b9b808190a1e8c283ba28d645 completed March 20, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69bd845f41f88190b75b8b64b9e41862 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:02 p.m.