Triple
T30023906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambda Muscae |
E762826
|
entity |
| Predicate | rotationalVelocity_km_per_s |
P69907
|
FINISHED |
| Object | 128 |
—
|
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: 128 | Statement: [Lambda Muscae, rotationalVelocity_km_per_s, 128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalVelocity_km_per_s Context triple: [Lambda Muscae, rotationalVelocity_km_per_s, 128]
-
A.
hasRotationalVelocityKmPerSec
chosen
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
B.
hasProjectedRotationalVelocity_kmPerS
Indicates the rotational speed an object appears to have along our line of sight, measured in kilometers per second.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679a9e95081908aecded7962e0c87 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:48 p.m.