Triple
T1342732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperion |
E28501
|
entity |
| Predicate | synchronousRotation |
P7284
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Hyperion, synchronousRotation, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synchronousRotation Context triple: [Hyperion, synchronousRotation, false]
-
A.
synchronizesWith
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
-
B.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
C.
rotationType
chosen
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
D.
equatorialRotationDirection
Indicates the direction in which an object rotates around its axis at the equator.
-
E.
rotatingLocation
Indicates that an entity is rotating around, or undergoing rotational motion at, a specified location or point in space.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2174d048190a6e9380df302265f |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.