Triple
T26296516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter’s magnetosphere |
E661432
|
entity |
| Predicate | rotationRegime |
P7284
|
FINISHED |
| Object | corotation-dominated inner magnetosphere |
—
|
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: corotation-dominated inner magnetosphere | Statement: [Jupiter’s magnetosphere, rotationRegime, corotation-dominated inner magnetosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationRegime Context triple: [Jupiter’s magnetosphere, rotationRegime, corotation-dominated inner magnetosphere]
-
A.
rotationType
chosen
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
B.
rotationProcess
Indicates a process in which something is turned or rotated around an axis or point over time.
-
C.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
D.
hasRotationMechanic
Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
-
E.
rotationStatus
Indicates the current state or condition of an entity’s rotation, such as whether and how it is rotating.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eaea1d08190b93b85590b8c9781 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:12 p.m.