Triple
T28249045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 32349 |
E712264
|
entity |
| Predicate | rotationVelocityProjected |
P137888
|
FINISHED |
| Object | about 16 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: about 16 km/s | Statement: [HIP 32349, rotationVelocityProjected, about 16 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationVelocityProjected Context triple: [HIP 32349, rotationVelocityProjected, about 16 km/s]
-
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.
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.
-
D.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
-
E.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643ee1a1881909a7f4588daba8eca |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:03 p.m.