Triple
T15880937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dactyl |
E385071
|
entity |
| Predicate | isAsynchronousWithIdaRotation |
P55126
|
FINISHED |
| Object | likely |
—
|
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: likely | Statement: [Dactyl, isAsynchronousWithIdaRotation, likely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAsynchronousWithIdaRotation Context triple: [Dactyl, isAsynchronousWithIdaRotation, likely]
-
A.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
B.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
C.
isAsynchronous
chosen
Indicates that the related process, operation, or interaction occurs without requiring simultaneous timing or immediate coordination between the involved entities.
-
D.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
E.
hasChaoticRotation
Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.