Triple
T6329773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Cancri |
E141949
|
entity |
| Predicate | hasRotationalVelocity_km_per_s |
P69907
|
FINISHED |
| Object | about 130 |
—
|
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 130 | Statement: [Gamma Cancri, hasRotationalVelocity_km_per_s, about 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotationalVelocity_km_per_s Context triple: [Gamma Cancri, hasRotationalVelocity_km_per_s, about 130]
-
A.
hasRotationalVelocityKmPerSec
chosen
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
B.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
-
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.
hasRotationCurve
Indicates that an object is associated with a rotation curve describing how its rotational velocity varies with radius or position.
-
E.
equatorialLinearSpeed
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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651334c08190a9514faa36e7812d |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.