Triple
T3098399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taygete |
E64655
|
entity |
| Predicate | hasRotationState |
P27379
|
FINISHED |
| Object | likely non-synchronous |
—
|
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 non-synchronous | Statement: [Taygete, hasRotationState, likely non-synchronous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotationState Context triple: [Taygete, hasRotationState, likely non-synchronous]
-
A.
hasChaoticRotation
chosen
Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
-
B.
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.
-
C.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
D.
hasFieldOrientation
Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
-
E.
hasSpin
Indicates that one entity possesses or exhibits rotational motion or angular momentum.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23dde988190a1aca020685594f3 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.