Triple
T6287161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 87 Tauri |
E140927
|
entity |
| Predicate | hasRotationalVelocityKmPerSec |
P69907
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [87 Tauri, hasRotationalVelocityKmPerSec, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotationalVelocityKmPerSec Context triple: [87 Tauri, hasRotationalVelocityKmPerSec, low]
-
A.
equatorialLinearSpeed
Indicates the linear (tangential) speed of a rotating body measured specifically at its equator.
-
B.
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.
-
C.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
D.
isRapidlyRotating
Indicates that an entity is spinning or rotating at a very high angular speed relative to a typical or reference rate.
-
E.
hasRelativeAngularMomentum
Indicates that one entity possesses angular momentum defined relative to another reference entity or frame.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.