Triple
T4959399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taygeta |
E111366
|
entity |
| Predicate | rotationalVelocity |
P51228
|
FINISHED |
| Object | high projected rotational velocity |
—
|
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: high projected rotational velocity | Statement: [Taygeta, rotationalVelocity, high projected rotational velocity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalVelocity Context triple: [Taygeta, rotationalVelocity, high projected rotational velocity]
-
A.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
B.
isRapidlyRotating
chosen
Indicates that an entity is spinning or rotating at a very high angular speed relative to a typical or reference rate.
-
C.
equatorialLinearSpeed
Indicates the linear (tangential) speed of a rotating body measured specifically at its equator.
-
D.
rotatingLocation
Indicates that an entity is rotating around, or undergoing rotational motion at, a specified location or point in space.
-
E.
equatorialRotationDirection
Indicates the direction in which an object rotates around its axis at the 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.