Triple
T3729455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20000 Varuna |
E79025
|
entity |
| Predicate | rotationCharacteristic |
P14493
|
FINISHED |
| Object | rapid rotation |
—
|
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: rapid rotation | Statement: [20000 Varuna, rotationCharacteristic, rapid rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationCharacteristic Context triple: [20000 Varuna, rotationCharacteristic, rapid rotation]
-
A.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
B.
rotationPractice
Indicates that an entity engages in or is involved with practicing rotational movements or rotation-related skills.
-
C.
hasChaoticRotation
Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
-
D.
movementCharacteristic
chosen
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
E.
rotatesWith
Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.